Am Mittwoch, 19. August 2015, 11:59:12 schrieb Bram Moolenaar: > > Markus Heidelberg wrote: > > > Am Dienstag, 18. August 2015, 18:42:50 schrieb Bram Moolenaar: > > > > > > I let the script continue, ignoring the errors. Then I pushed the > > > result to github. I got some errors, I think my sequence of commands is > > > not quite right, probably some can be left out: > > > > > > % git remote add origin [email protected]:vim/vim.git > > > % git remote -v > > > % git push --mirror > > > % git push --set-upstream origin master > > > % git push --tags > > > % git push origin :origin/master > > > > Should be ok. Tried locally and it looked good, I only got an error with > > the last command because the branch "origin/master" did not exist yet on > > the remote repository and could not be deleted. > > So I just leave out the last command?
Yes, it is not necessary in this command sequence because there did not yet exist a remote master branch you could have pushed in addition to the normal master branch. But it doesn't harm either. > > > The result is now at https://github.com/vim/vim. It does have > > > everything up to patch 7.4.827. Does it look OK? > > > > Not quite. Apart from the wrong tag naming there is also a wrong merge > > order in the two merge commits (obtain them with "git log --merges"), > > which already was the case with the direct Google Export. > > Yes, this is the result of the Google export. Or GitHub import from > Google Code, as the conversion is actually done by GitHub. No, this was indeed the result of your local conversion using the old hg-fast-export package and the cleanup. Before you renamed it from vim/vim to vim/vim-tryout. However... > > You said you use the Ubuntu package. I had a look: > > http://packages.ubuntu.com/source/vivid/hg-fast-export > > Even in the latest Ubuntu version 15.04, the package is from 2014-03-08, > > despite having received changes upstream until October 2014. The merge > > order problem has been fixed during that time (log: "do not sort merge > > commit parents"). The same version is used on Debian unstable Sid. > > > > A bit disappointing that obviously an old distro package is used for the > > Google Exporter. As you wrote above, the conversion is done by GitHub. I read it today on the Google Code shutdown announcement: "Please note: GitHub’s importer will convert any Subversion or Mercurial Google Code projects to use Git in the process." http://google-opensource.blogspot.de/2015/03/farewell-to-google-code.html So it's GitHub who uses an old fast-export version and omits the packfile optimization. They should know better. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
