From: "Han-Wen Nienhuys" <hanwenn@gmail.com>
To: git@vger.kernel.org
Subject: git-rev-list diff options broken
Date: Tue, 6 Nov 2007 19:14:14 -0300 [thread overview]
Message-ID: <f329bf540711061414k1627521bvaf4a7a06460cc3fd@mail.gmail.com> (raw)
Hi,
the git-rev-list manpage says
**
Diff Formatting
~~~~~~~~~~~~~~~
Below are listed options that control the formatting of diff output.
Some of them are specific to gitlink:git-rev-list[1], however other diff
options may be given. See gitlink:git-diff-files[1] for more options.
**
however, the source code says
if ((!list &&
(!(revs.tag_objects||revs.tree_objects||revs.blob_objects) &&
!revs.pending.nr)) ||
revs.diff)
usage(rev_list_usage);
so any attempt at showing diffs with git-rev-list will fail. What's
the deal with this?
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next reply other threads:[~2007-11-06 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 22:14 Han-Wen Nienhuys [this message]
2007-11-06 22:15 ` git-rev-list diff options broken 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
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=f329bf540711061414k1627521bvaf4a7a06460cc3fd@mail.gmail.com \
--to=hanwenn@gmail.com \
--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).