On Thu, Aug 21, 2014 at 02:57:22PM -0700, Junio C Hamano wrote:
> Jeff King <p...@peff.net> writes:
> > +--anonymize::
> > + Replace all paths, blob contents, commit and tag messages,
> > + names, and email addresses in the output with anonymized data,
> > + while still retaining the shape of history and of the stored
> > + tree.
> Sometimes branch names can contain codenames the project may prefer
> to hide from the general public, so they may need to be anonymised
> as well.
Yes, I do anonymize them (and check it in the tests). See
anonymize_refname. I just forgot to include it in the list. Trivial
squashable patch is below.
The few things I don't anonymize are:
1. ref prefixes. We see the same distribution of refs/heads vs
2. refs/heads/master is left untouched, for convenience (and because
it's not really a secret). The implementation is lazy, though, and
would leave "refs/heads/master-supersecret", as well. I can tighten
that if we really want to be careful.
3. gitlinks are left untouched, since sha1s cannot be reversed. This
could leak some information (if your private repo points to a
public, I can find out you have it as submodule). I doubt it
matters, but we can also scramble the sha1s.
diff --git a/Documentation/git-fast-export.txt
index 0ec7cad..52831fa 100644
@@ -106,10 +106,10 @@ marks the same across runs.
different from the commit's first parent).
- Replace all paths, blob contents, commit and tag messages,
- names, and email addresses in the output with anonymized data,
- while still retaining the shape of history and of the stored
+ Replace all refnames, paths, blob contents, commit and tag
+ messages, names, and email addresses in the output with
+ anonymized data, while still retaining the shape of history and
+ of the stored tree.
Apply the specified refspec to each ref exported. Multiple of them can
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html