Markus Heidelberg wrote: > > > OK, then I would document a procedure for local HG to Git conversion and > > > create a script for Git repository cleanup. > > > > I did: > > > > % mkdir vim-git > > % cd vim-git > > % git init > > % hg-fast-export -r ../hg-vim74-clean > > On Arch Linux I had to set PYTHON=python2 for this command because the > default "python" is a symbolic link to python3. > > > % git checkout > > And then, as written in my previous mail, additionally: > > % git repack -a -d -f > % git gc
OK. > I guess you got the hg-fast-export from one of these locations? > http://repo.or.cz/w/fast-export.git > https://github.com/frej/fast-export On Ubuntu it's a package that can be installed. > > Looks like it worked. I have replaced the "vim" repository on github > > with the cleaned up and locally converted repository. > > Please have a look: https://github.com/vim/vim > > I aborted the clone, despite not having to wait too long for it to > complete, but maybe you can create a new repo with the packfile > optimization applied. > From a quick look online, it seems fine. > > I saw you added the .gitignore already in the HG repo. I rather thought > of creating it as part of the cleanup based on .hgignore, then for the > whole history since addition of .hgignore. However, this can still be > done. I thought the .gitignore is useful anyway. It was only sitting in the git repo so far, and to avoid the first version of that being "broken" I thought it would be good to include now. > I'd also prefer to just removing the .hgignore from the history and > replacing it with .gitignore. What would that mean for the HG mirror, > Christian? I'm not sure what happens when mirrorring the git repo to Mercurial. If it converts the .gitignore to .hgignore an existing .hgignore might be a problem maybe? > > I have commited one new patch on top of it to check if that works. > > It looks OK, but I got a long list of messages like this: > > > > ... > > * [new tag] v7-4-823 -> v7-4-823 > > * [new tag] v7-4-824 -> v7-4-824 > > * [new tag] v7-4-825 -> v7-4-825 > > * [new tag] v7-4a -> v7-4a > > * [new tag] v7-4a-001 -> v7-4a-001 > > * [new tag] v7-4a-002 -> v7-4a-002 > > * [new tag] v7-4a-003 -> v7-4a-003 > > ... > > * [new tag] v7-4b-019 -> v7-4b-019 > > * [new tag] v7-4b-020 -> v7-4b-020 > > * [new tag] v7-4b-021 -> v7-4b-021 > > * [new tag] v7-4b-022 -> v7-4b-022 > > These messages occur for all the tags that have just been pushed. > > > Perhaps the original push to github should have been followed by "push > > --tags" ? Not sure if it makes any difference doing this after another > > commit+push. > > For the repository it doesn't make a difference if you forgot to push > the tags and do it later after unrelated commits. These are all > lightweight tags, just labels/pointers to a specific commit and not tied > to the history tree (DAG) at all. > The users would receive the missing tags with the next "git fetch". OK, so doing it earlier just makes it nicer. > > Please let me know if this looks OK. If yes then I'll do it for real > > this weekend. > > What do you mean with real? Only publishing the HG cleanup? > Because for the Git cleanup I have to prepare the script first. OK, I'll have to wait for that then. With "for real" I mean that we tell everybody to switch to the new repository and we stop updating the old one on Google code. -- FATHER: You only killed the bride's father - that's all - LAUNCELOT: Oh dear, I didn't really mean to... FATHER: Didn't mean to? You put your sword right through his head! LAUNCELOT: Gosh - Is he all right? "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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.
