On 3 April 2013 10:25, Ralf Hemmecke <hemme...@gmail.com> wrote: > On 04/03/2013 03:06 PM, Jordi Gutiérrez Hermoso wrote: >> You can use hg-git to keep working with hg and pushing to a git >> upstream. There is no need to understand the abstruse git interface >> this way and you can stay with the familiar hg interface. You will >> however need to learn how hg bookmarks map to git branches, but you >> don't need to know the difference between --hard --soft --mixed >> --merge or --keep resets, nor do you need to worry about mapping local >> tracking branches to remote branches, nor will you need to go digging >> in reflogs if you mess up an operation, nor any other other >> gitological operation. >> >> I am working on improving hg-git. If you run into trouble with it, >> please let me know. > > Maybe you have a better version of hg-git, but note that due to the > nature of hg-git, if one clones such a hg repository, it is no longer > connected to the original git repository. I guess that causes much more > trouble than learning git properly.
This is a possible improvement to hg-git, but not a problem that I've faced myself. I keep in mind which clone is the one tied to the git upstream. If the sage-combinat-devel people face this problem, I will work on improving hg-git this way. I have stripped the rest of your gitology. Yes, git can be learned, but if you already know hg, it doesn't have to be, and our goal here is to hack on Sage, not to learn gitology. - Jordi G. H. -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
