Re: [PATCH v2 01/12] fast-export: do anonymize the primary branch name

From: Jeff King <peff@peff.net>
Date: Jun 17, 2020, 21:23 UTC
Message-ID: <20200617212333.GB2809@coredump.intra.peff.net>
In-Reply-To: <xmqqmu51v9qy.fsf@gitster.c.googlers.com>

On Wed, Jun 17, 2020 at 11:16:05AM -0700, Junio C Hamano wrote:

Show 13 quoted lines

> Jeff King <peff@peff.net> writes:
> 
> > Of course that only helps you for _one_ branch. A more generally useful
> > mechanism would be to teach fast-export to write the ref mapping (and
> > perhaps file mappings, etc) to a separate file. Then you could convert
> > any reproduction recipe to use the anonymized names, and share only that
> > recipe along with the anonymized dump. But that's _way_ outside the
> > scope of your series. This seems like a good interim step to retain the
> > status quo.
> 
> Actually, dropping this special case, and dropping the other special
> case with fmt-merge-msg, we can do without the notion of the
> "primary" branch.

That leaves us in the interim with a "fast-export --anonymize" that is a little harder to use (you have no way to know which branch was which).

But I don't mind at all implementing the map-dumping feature to help move this along. As long as both make it into the same release, then fast-export only gets better, and never regresses. :)

-Peff