From: Brian Gernhardt <benji@silverinsanity.com>
To: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Change in git-svn dcommit semantics?
Date: Fri, 22 Dec 2006 09:09:01 -0500 [thread overview]
Message-ID: <3EB63EEE-0F78-47CE-B94E-325A9F6817C5@silverinsanity.com> (raw)
In-Reply-To: <20061220115731.GA29786@coredump.intra.peff.net>
On Dec 20, 2006, at 6:57 AM, Jeff King wrote:
> 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
next prev parent reply other threads:[~2006-12-22 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 21:12 Change in git-svn dcommit semantics? Seth Falcon
2006-12-19 22:09 ` Eric Wong
2006-12-20 3:05 ` Seth Falcon
2006-12-19 23:02 ` Brian Gernhardt
2006-12-19 23:57 ` Johannes Schindelin
2006-12-20 0:38 ` Brian Gernhardt
2006-12-20 0:52 ` Jakub Narebski
2006-12-20 1:17 ` Junio C Hamano
2006-12-20 11:38 ` Jakub Narebski
2006-12-20 11:47 ` Brian Gernhardt
2006-12-20 11:57 ` Jeff King
2006-12-22 14:09 ` Brian Gernhardt [this message]
2006-12-20 3:07 ` Seth Falcon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EB63EEE-0F78-47CE-B94E-325A9F6817C5@silverinsanity.com \
--to=benji@silverinsanity.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).