From: Theodore Tso <tytso@mit.edu>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Any objectsions to enhancing git-log to show tags/branch heads?
Date: Mon, 16 Apr 2007 23:15:52 -0400 [thread overview]
Message-ID: <20070417031552.GA18373@thunk.org> (raw)
In-Reply-To: <f01b9g$qqc$1@sea.gmane.org>
On Tue, Apr 17, 2007 at 04:30:47AM +0200, Jakub Narebski wrote:
> You have to use --abbrev-commit (--abbrev is opassed to log machinery, and
> covers object ids), which is undocumented option (mentioned only in passing
> in git-reflog(1)).
Sigh, I found --abbrev first from deferencing the following paragraph
from the git-log man page:
The [git-log] command takes options applicable to the
git-rev-list(1) command to control what is shown and how, and
options applicable to the git-diff-tree(1) commands to control how
the changes each commit introduces are shown.
In any case, --abrev is mentioned in git-rev-list(1)'s man page, and
specifying it doesn't cause git-log to bomb out with an illegal option
name. It just apparently ignores it as far as I can tell.
- Ted
prev parent reply other threads:[~2007-04-17 3:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 12:45 Any objectsions to enhancing git-log to show tags/branch heads? Theodore Ts'o
2007-04-16 17:46 ` Junio C Hamano
2007-04-16 20:46 ` Theodore Tso
2007-04-16 18:13 ` Peter Baumann
2007-04-16 18:27 ` J. Bruce Fields
2007-04-17 5:07 ` Peter Baumann
2007-04-17 13:36 ` J. Bruce Fields
2007-04-16 19:01 ` Julian Phillips
2007-04-17 5:08 ` Peter Baumann
2007-04-16 23:00 ` Linus Torvalds
2007-04-17 2:21 ` Theodore Tso
2007-04-17 2:30 ` Jakub Narebski
2007-04-17 3:00 ` Linus Torvalds
2007-04-23 10:00 ` Junio C Hamano
2007-04-17 3:15 ` Theodore Tso [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=20070417031552.GA18373@thunk.org \
--to=tytso@mit.edu \
--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.
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).