Markus Heidelberg wrote: > if switching to Git, we could seriously consider cleaning up the > repository, now it might be the last chance for quite a while. > > I have collected some possibilities for improvement - some simple, some > a bit more complicated, but if found the proper commands/scripts, the > automated tasks should work without much hassle.
[...] I generally like cleaning up, but at the same time we should not spend time on things nobody will really care about. Adding tags to old commits is not very useful. In fact, github already has a problem with the number of tags that Vim has. Removing empty and useless meta data sounds useful. Branches were only used temporarily, I don't think they contain useful information. I don't think I will want to change the commit messages because some git tools can't handle them properly. AFAIK the message do show up properly in most places. Some things can perhaps be done on the Mercurial repository before the import, but I suppose some are only possible in git. What will happen for the mirror in Mercurial then? We need to make sure we don't break anything. -- There are only two hard things in programming: Cache invalidation, naming things and off-by-one errors. /// 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.
