On Sat, Mar 11, 2023 at 1:11 PM Uwe Brauer <o...@mat.ucm.es> wrote:
> > On Thu, Mar 9, 2023 at 8:07 PM Felipe Contreras
> > <felipe.contre...@gmail.com> wrote:
> > FWIW I updated the patches and sent them to the dev mailing list so
> > they stay on the record:
> > https://lore.kernel.org/git/camp44s0cbum1jzyp57ninikwsxg9kugbkdaoozmnen1akvg...@mail.gmail.com/T/#t
> I just skimmed over the thread. It seems that the reactions were not
> negative, so there is some hope.

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.

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.

> Concerning mercurial topics, well it is part of the evolve extension,
> which is not part of mercurial core, but on the other hand the evolve
> extension is now quite stable so I would not call it experimental, but
> anyhow never mind.
> Exporting named branches to git branches (for the hg-git extension) is
> unfortunately experimental.

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.

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.


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

Felipe Contreras

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 

Reply via email to