Re: Change in git-svn dcommit semantics?

From: Brian Gernhardt <benji@silverinsanity.com>
Date: Dec 22, 2006, 14:09 UTC
Message-ID: <3EB63EEE-0F78-47CE-B94E-325A9F6817C5@silverinsanity.com>
In-Reply-To: <20061220115731.GA29786@coredump.intra.peff.net>

On Dec 20, 2006, at 6:57 AM, Jeff King wrote:

Show 16 quoted lines

> On Wed, Dec 20, 2006 at 06:47:45AM -0500, Brian Gernhardt wrote:
>
>>>> The --full-diff option helps because it shows the diff for other
>>>> files (that do not have different number of substring COLLISION
>>>> in the pre and postimage) in the same commit as well.
>>>
>>> Yet another undocumented option. Sigh...
>>
>> I'd send in a patch to fix that (little gnome work is what I do in
>> Wikipedia, and seems to be what I do here), but the option seems to
>> be in setup_revision.c:setup_revisions, which is used in several
>> places.  Is there a central place to put that in the documentation?
>> Should there be?
>
> Please read the rest of the thread for some explanation from Junio on
> how this option works.

I was trying to write quick documentation for this option, placing it in Documentation/diff-options.txt (is that the right place for it?), when I ran across --pickaxe-all. How do the two options differ?

~~ Brian