Re: [PATCH] teach fast-export an --anonymize option

2014-08-21 Thread Jeff King
On Thu, Aug 21, 2014 at 02:57:22PM -0700, Junio C Hamano wrote: > Jeff King 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 an

Re: [PATCH] teach fast-export an --anonymize option

2014-08-21 Thread Jeff King
On Thu, Aug 21, 2014 at 01:15:10PM -0700, Junio C Hamano wrote: > Jeff King writes: > > > +/* > > + * We anonymize each component of a path individually, > > + * so that paths a/b and a/c will share a common root. > > + * The paths are cached via anonymize_mem so that repeated > > + * lookups fo

Re: [PATCH] teach fast-export an --anonymize option

2014-08-21 Thread Junio C Hamano
Jeff King 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 coden

Re: [PATCH] teach fast-export an --anonymize option

2014-08-21 Thread Junio C Hamano
Jeff King writes: > +/* > + * We anonymize each component of a path individually, > + * so that paths a/b and a/c will share a common root. > + * The paths are cached via anonymize_mem so that repeated > + * lookups for "a" will yield the same value. > + */ > +static void anonymize_path(struct st

[PATCH] teach fast-export an --anonymize option

2014-08-21 Thread Jeff King
Sometimes users want to report a bug they experience on their repository, but they are not at liberty to share the contents of the repository. It would be useful if they could produce a repository that has a similar shape to its history and tree, but without leaking any information. This "anonymize