<p><a href="http://www.github.com/MichaelBlume/pypy">http://www.github.com/MichaelBlume/pypy</a></p>
<p>Got it on a 10 minute cron</p>
<p>Note that this is *not* hash-compatible with the previous git mirror -- something changed in the hg-git implementation since that was started.</p>
<div class="gmail_quote">On May 5, 2012 12:59 AM, "Michael Blume" <<a href="mailto:blume.mike@gmail.com">blume.mike@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sebastien: See my remark to Yury. Mercurial *actively* annotates your<br>
commits with information about what branch you were on when you made<br>
the commit. Git users can, of course, add this information, they just<br>
have to do it manually.<br>
<br>
Ronny: As I said, it's *really easy* to construct git commits which,<br>
when translated, come out on a named branch.<br>
<br>
On Sat, May 5, 2012 at 12:44 AM, Sebastien Douche <<a href="mailto:sdouche@gmail.com">sdouche@gmail.com</a>> wrote:<br>
> On Fri, May 4, 2012 at 9:06 PM, Ronny Pfannschmidt<br>
> <<a href="mailto:Ronny.Pfannschmidt@gmx.de">Ronny.Pfannschmidt@gmx.de</a>> wrote:<br>
>>> Um, what is "named branches" thing that git apparently doesn't have?<br>
>><br>
>> named branches are branches that are part of the history<br>
>> git branches are only pointers, not part of the history<br>
><br>
> Uh?! Non sense. Both backend have the full DAG.<br>
><br>
> --<br>
> Sebastien Douche <<a href="mailto:sdouche@gmail.com">sdouche@gmail.com</a>><br>
> Twitter: @sdouche / G+: +sdouche<br>
> _______________________________________________<br>
> pypy-dev mailing list<br>
> <a href="mailto:pypy-dev@python.org">pypy-dev@python.org</a><br>
> <a href="http://mail.python.org/mailman/listinfo/pypy-dev" target="_blank">http://mail.python.org/mailman/listinfo/pypy-dev</a><br>
</blockquote></div>