Hi, On Wed, 10 Jun 2020, Junio C Hamano wrote: > Matt Rogers <mattr94@xxxxxxxxx> writes: > > > I think that's not very convincing. If branch names in general are identifying > > enough to warrant anonymization then shouldn't the default name be too? > > It is a good argument. I also heard a rumor that often branch names > contain codewords given to pre-released hardware that are highly > confidential in certain circles, and heard that it is one of the > reasons why Gerrit has server side ACL that lets you hide some > branches from authenticated users that can access other branches. Yes, branch names in general _can_ contain information users may prefer to keep private. However, we're not talking about branch names in general. We are talking about the default name of the main branch, to be picked in _all_ of your new repositories. > Again, the original comment explains why 'master' without such a > configuration knob was not worth protecting, but what it does not > explain is why keeping it (and only that branch name) unmunged gives > a more useful result than munging everything. From the point of > view of "I want to debug the shape of the DAG, without the actual > user data", munging 'master' to 'ref47' while other branches like > 'next' are munged to 'ref%d' does not make it harder to use or less > useful for the debugging than only 'master' is kept intact in the > output stream. Yes. And you're unlikely to configure the default name to be used for all of your future `git init` operations to be something non-generic. I am still highly doubtful of Matt's suggestion that it would be worth protecting the default name of the main branch to be used for _each_ and _any_ new repository. Now, if you suggest that `git fast-export --anonymize` should either not special-case the main branch, or at least have a configurable set of names it skips from protecting, then I will be much more in favor of those suggestions. However, those suggestions are quite a bit orthogonal to the patch series at hand, so I would want to discuss them in their own code contribution instead of here. Ciao, Dscho
