On Sun, Aug 31, 2014 at 06:34:08AM -0400, Eric Sunshine wrote:
> >> I feel like this should be part of git-fast-export.txt, just to
> >> increase the user's confidence in the tool (and I don't expect most
> >> users to read this commit message).
> >
> > Hmph. Whenever I say "I think this patch is
On Thu, Aug 28, 2014 at 8:32 AM, Jeff King wrote:
> On Thu, Aug 28, 2014 at 05:30:44PM +0700, Duy Nguyen wrote:
>
>> On Thu, Aug 28, 2014 at 12:01 AM, Jeff King wrote:
>> > You can get an overview of what will be shared
>> > by running a command like:
>> >
>> > git fast-export --anonymize --all
On Thu, Aug 28, 2014 at 11:11:47AM -0700, Junio C Hamano wrote:
> > + Anonymize the contents of the repository while still retaining
> > + the shape of the history and stored tree. See the section on
> > + `ANONYMIZING` below.
>
> Technically s/tree/trees/, I would think. For a repository
On Thu, Aug 28, 2014 at 05:46:15PM +0100, Ramsay Jones wrote:
> Dumb question (I have not even read the patch, so please just ignore me
> if this is indeed dumb!): Is the map of
> available to the user while he attempts to confirm that the bug is still
> present?
No, it's not.
> For example, if
Ramsay Jones writes:
> Dumb question (I have not even read the patch, so please just ignore me
> if this is indeed dumb!): Is the map of
> available to the user while he attempts to confirm that the bug is still
> present?
>
> For example, if I anonymized git.git, and did 'git branch -v' (say),
Jeff King writes:
> Subject: docs/fast-export: explain --anonymize more completely
>
> The original commit made mention of this option, but not why
> one might want it or how they might use it. Let's try to be
> a little more thorough, and also explain how to confirm that
> the output really is a
On 28/08/14 13:32, Jeff King wrote:
> On Thu, Aug 28, 2014 at 05:30:44PM +0700, Duy Nguyen wrote:
>
>> On Thu, Aug 28, 2014 at 12:01 AM, Jeff King wrote:
>>> You can get an overview of what will be shared
>>> by running a command like:
>>>
>>> git fast-export --anonymize --all |
>>> perl -pe
On Thu, Aug 28, 2014 at 05:30:44PM +0700, Duy Nguyen wrote:
> On Thu, Aug 28, 2014 at 12:01 AM, Jeff King wrote:
> > You can get an overview of what will be shared
> > by running a command like:
> >
> > git fast-export --anonymize --all |
> > perl -pe 's/\d+/X/g' |
> > sort -u |
> > less
On Thu, Aug 28, 2014 at 12:01 AM, Jeff King wrote:
> You can get an overview of what will be shared
> by running a command like:
>
> git fast-export --anonymize --all |
> perl -pe 's/\d+/X/g' |
> sort -u |
> less
>
> which will show every unique line we generate, modulo any
> numbers (each
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
10 matches
Mail list logo
