> On Sat, Mar 11, 2023 at 1:11 PM Uwe Brauer <o...@mat.ucm.es> wrote:

> You are a much more positive person than me. I've had countless
> discussions with positive reactions who lead to nothing. It seems this
> is going to be another one of those.

Or just more naive.... 😉

> After just one reply it has been completely ignored. I guess if Google
> or Microsoft isn't going to pay for this no git developer is going to
> bother taking a look at it.

> I wrote the equivalent of hg-git for the git world: git-remote-hg [1],
> and there exporting named branches works fine. They have the
> "branches/" prefix and only one head is tracked.

Do you mean exporting named hg branches into git branches? Yes that seems ok, 
the other way around is the challenge, but the current hg-git developers want 
to focus on improving hg bookmarks, but this is a promise that has been around 
for ages, with very little progress, if any at all. 

> Of course they are not commit labels like in hg, but a hack can be
> enabled to store the name of the branch on every commit like hg-git
> does with the hg-git-compat option.

> I don't personally care about that but the option is there for those who do.

Which is good.

> Cheers.

> [1] https://github.com/felipec/git-remote-hg

Warning: Content may be disturbing to some audiences
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine. 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to