From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Bill Lear <rael@zopyra.com>, git@vger.kernel.org
Subject: Re: How to say HEAD~"all the way back - 1"
Date: Thu, 22 Feb 2007 15:47:37 -0500 [thread overview]
Message-ID: <20070222204737.GC18622@fieldses.org> (raw)
In-Reply-To: <7vodnmdk8y.fsf@assigned-by-dhcp.cox.net>
On Thu, Feb 22, 2007 at 12:12:45PM -0800, Junio C Hamano wrote:
> Sorry, there is no such shorthand, but you could obviously say:
>
> $ git rev-list --parents HEAD | grep -v ' '
>
> A way to find the root commit seems to be one of the things
> people new to git want at least once, once they start futzing
> with the tool. But I suspect that is only because they need
> that information to see how the tool works (say "what different
> output would I get out of 'git show $commit' for root and other
> commits?"), and not because they need that information for any
> real life use.
>
> Really, what useful purpose does it serve for you to find out
> the root commit, OTHER THAN being able to say "the development
> history of this project starts at this commit"?
I occasionally want to reference commits not relative to "all the way
back" but to "all the way back on this branch". So, e.g., what's the
next-to-last commit before "topic" meets up with "origin"?
I can do something like
git rev-list origin..topic | tail -2 | head -1
but in practice it's faster just to fire up gitk origin.. and
cut-n-paste object id's.
--b.
next prev parent reply other threads:[~2007-02-22 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 19:17 How to say HEAD~"all the way back - 1" Bill Lear
2007-02-22 19:36 ` Petr Baudis
2007-02-23 17:52 ` Jakub Narebski
2007-02-23 17:56 ` Bill Lear
2007-02-24 9:30 ` Junio C Hamano
2007-02-22 20:12 ` Junio C Hamano
2007-02-22 20:24 ` Bill Lear
2007-02-22 20:59 ` Junio C Hamano
2007-02-22 20:47 ` J. Bruce Fields [this message]
2007-02-22 20:53 ` 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=20070222204737.GC18622@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=rael@zopyra.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).