Thread (1 message) 1 message, 1 author, 2020-06-12

Re: Re* [PATCH 8/9] fast-export: respect the possibly-overridden default branch name

From: Junio C Hamano <hidden>
Date: 2020-06-12 12:50:15

Johannes Schindelin [off-list ref] writes:
quoted
Subject: [PATCH] fast-export: do anonymize the primary branch name
I like this approach a lot. Do you want me to integrate it into this patch
series, or rather have it as a stand-alone patch?
I do not see any need for an off-series preparation step.  Without
configurable primary branch, keeping 'master' as 'master' used in
the current code is an OK way to anonymize refs and still keep the
primary line of development in the output identifyable.  The "ref0"
trick becomes necessary only when we introduce configurable primary;
even though it would not hurt to switch to the "ref0" approach to
anonymize-but-still-the-primary-is-identifiable early, it just is
not necessary to do so.

I'd say that we should take [ref]
with two changes,

 - see if the "refname" matches the fully
   spelled primary branch name by asking repo_main_branch_name(repo,
   0), instead of comparing with "refs/heads/master", and

 - if matches return "refs/heads/ref0" instead of "ref0".

and replace your [PATCH 8/9] (or whichever the counterpart patch is
in the rerolled series) with it.

Thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help