From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: hanwen@xs4all.nl
Cc: git@vger.kernel.org
Subject: Re: git-rev-list diff options broken
Date: Tue, 6 Nov 2007 23:55:28 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711062354070.4362@racer.site> (raw)
In-Reply-To: <f329bf540711061538l4cdef27co2cb42a9938b2e325@mail.gmail.com>
Hi,
On Tue, 6 Nov 2007, Han-Wen Nienhuys wrote:
> 2007/11/6, Johannes Schindelin <Johannes.Schindelin@gmx.de>:
>
> > Probably you want to use "git log".
> >
> > "git blame -L 585,589 builtin-rev-list.c" indicates that 8c1f0b44(Fix
> > up rev-list option parsing) was responsible, which in turn indicates
> > that it was intentional.
>
> OK. So the man page needs fixing, right?
I guess. Although it seems a bit involved, since the diff-formats.txt are
not included by git-rev-list.txt itself, but by pretty-formats.txt.
Ciao,
Dscho
prev parent reply other threads:[~2007-11-06 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 22:14 git-rev-list diff options broken Han-Wen Nienhuys
2007-11-06 22:15 ` Han-Wen Nienhuys
2007-11-06 23:33 ` Johannes Schindelin
2007-11-06 23:38 ` Han-Wen Nienhuys
2007-11-06 23:55 ` Johannes Schindelin [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0711062354070.4362@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/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.
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 NNTP newsgroup(s).