[working workflow for importing git to a named branch] (was: graft/rebase without changing the hash)

[Dr. Arne Babenhauserheide]

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.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1125 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20221126/54574e6b/attachment-0001.asc>