[working workflow for importing git to a named branch]

[Uwe Brauer]

>>> "AB" == Arne Babenhauserheide <arne_bab at web.de> writes:

> Uwe Brauer <oub at mat.ucm.es> writes:

>>> It sounds like what you want is to have the resulting git-hash equal,
>>> not to have the Mercurial-hash equal. This could in theory be possible
>>> (because the branch name is not part of the hash-generation in git), but
>>> I do not know whether it is possible in practice.
>> 
>> The following surprisingly works, how stable it is I am not sure
>> 
>> * Workflow
>> 
>> The following works
>> 
>> ** HG
>> 1) create a hg repository.
>> 2) create a named branch main (because this is what github uses now)

> Could you just set a bookmark named main?
> That way you would still be on the branch used by hg-git as target for
> the default branch.

That is a misunderstanding, I do want to use named branch, especially I
want to know how to interact with git if more branches are going to be
used, either from my side or from git's side. 
I really dislike bookmarks and find them confusing.

That is why I am also flirting with the changesets in hg-git I mentioned
that allow to export named branches. The real challenge is to import git
branches into named branches, rebasing with evolve seems to work, I wounder how
stable that workflow will be.



Uwe 

> Best wishes,
> Arne

-- 
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. 
https://addons.thunderbird.net/en-US/thunderbird/addon/gmail-conversation-view/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5673 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20221126/f3512dee/attachment-0002.p7s>