Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

Only 8 of 230 commits migrated on d7ux project #44

Closed
GoogleCodeExporter opened this issue Apr 25, 2016 · 4 comments
Closed

Only 8 of 230 commits migrated on d7ux project #44

GoogleCodeExporter opened this issue Apr 25, 2016 · 4 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Migrated project d7ux from google code to github.
2. https://code.google.com/p/d7ux/source/list?num=25&start=230 shows it has 230 
commits
3. https://github.com/goba/d7ux/commits/master shows the migrated one has 8 
commits

What is the expected output? What do you see instead?

230 commits migrated.

What version of the product are you using? On what operating system?

Used the github migration tool provided.

Please provide any additional information below.

Attempted to fix the authors but a local checkout of the repo does not reveal 
more commits either.

Original issue reported on code.google.com by gabor.ho...@gmail.com on 16 Mar 2015 at 3:25

@GoogleCodeExporter
Copy link
Author

I removed the github project and ran the migration again today. Same result.

Original comment by gabor.ho...@gmail.com on 16 Mar 2015 at 3:26

@GoogleCodeExporter
Copy link
Author

I've reported this to our contacts at GitHub, this seems like a bug on their 
end.

Original comment by jasonhall@google.com on 16 Mar 2015 at 9:06

  • Changed state: Accepted
  • Added labels: Component-ExporterTool, Service-GitHub

@GoogleCodeExporter
Copy link
Author

Thanks, please keep me updated!

Original comment by gabor.ho...@gmail.com on 17 Mar 2015 at 8:05

@GoogleCodeExporter
Copy link
Author

This seems to have been caused by the reset of /trunk in 
https://code.google.com/p/d7ux/source/detail?r=221

All of those commits are still in the migrated repo though. You can see them in 
refs/import/raw:

$ git clone --mirror https://github.com/goba/d7ux
$ git rev-list refs/import/raw | wc -l
     230

The master branch of your migrated repo goes back to when /trunk was reset.

Original comment by jasonhall@google.com on 17 Mar 2015 at 3:01

  • Changed state: Done

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant