>>> "FC" == Felipe Contreras <felipe.contre...@gmail.com> writes:

> On Thu, Mar 16, 2023 at 3:26 PM Uwe Brauer <o...@mat.ucm.es> wrote:
>> > 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,

> No, I mean from git to hg.

> If a ref has a "branches/" prefix, it's considered an hg branch, and
> all the commits pushed to that branch get tagged.

Let me try to get this straight.

    1. Suppose there is a mercurial repository in say sourceforge, that
       contains two named branches:, default and stable.

    2. You clone that repository with your plugin into a git repository.
       I presume the named branches end up in the corresponding git

    3. You make two commits on default and three commit on the stable branch.

    4. You push (since you have write access), and all commits end up
       in the correct named hg branch?

    5. What happens if you create an additional git branch, say bug-fix
       and make a couple of commits and  push. Do they end up as a new
       named branch called bug-fix, or as a bookmark, or can you chose
       between both?

    6. What's about topics, do you also support these?

Well 6. is not that important, but if the workflow described in 1-5 is
true, then that would be excellent and solve quite some problems on my
side. That would be,  as the US-Americans say, awesome.

I would use your plugin to pull from a git repository and would push then to
my local hg repository.

Thanks and regards

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