From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeff King <peff@peff.net>, Bill Lear <rael@zopyra.com>,
git@vger.kernel.org
Subject: Re: Listing of branch creation time?
Date: Tue, 27 Mar 2007 19:04:18 -0700 [thread overview]
Message-ID: <7vd52um8d9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0703271759510.6730@woody.linux-foundation.org> (Linus Torvalds's message of "Tue, 27 Mar 2007 18:06:11 -0700 (PDT)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Tue, 27 Mar 2007, Jeff King wrote:
>>
>> You have to look at the latest merge-base, but that tells you the last
>> time you merged with master, not necessarily the first time.
>
> Well, if you know which branch it is a branch off of, don't use
> merge-base, just do
>
> git log --reverse -1 origin..branch
>
> which should pick up the first commit that is on that branch but haven't
> been merged back to the original branch.
I suspect you fell into the common trap of confused interaction
between --max-count and --reverse here. This will show the
latest one commit on the branch that is still not in origin.
Similarly, "git log --reverse -1 master" is _not_ the way to
find the root commit of the project.
> (Personally, if I didn't want the graphical version, I'd likely just do
>
> git log origin..branch
>
> and then do '>' in the pager to get to the bottom. That way I can then
> scroll up and down if I decide I want to get a bigger picture)
What I use myself is git-topic.perl script from the 'todo'
branch. It essentially is:
for topic
do
git [short]log --no-merges master..$topic
done
with frills.
next prev parent reply other threads:[~2007-03-28 2:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 21:52 Listing of branch creation time? Bill Lear
2007-03-27 23:03 ` [PATCH] git-branch: add --sort-by-date option Johannes Schindelin
2007-03-27 23:53 ` Bill Lear
2007-07-23 23:38 ` [PATCH] Teach revision machinery about --no-walk Johannes Schindelin
2007-03-27 23:35 ` Listing of branch creation time? Jeff King
2007-03-28 0:00 ` Bill Lear
[not found] ` <2007032 8000149.GA12808@coredump.intra.peff.net>
2007-03-28 0:01 ` Jeff King
2007-03-28 0:08 ` Bill Lear
2007-03-28 0:10 ` Jeff King
2007-03-28 0:14 ` Bill Lear
2007-03-27 23:51 ` David Lang
2007-03-28 0:21 ` Jeff King
2007-03-28 1:29 ` Nicolas Pitre
2007-03-28 1:25 ` Nicolas Pitre
2007-03-28 1:06 ` Linus Torvalds
2007-03-28 2:04 ` Junio C Hamano [this message]
2007-03-28 2:52 ` Jeff King
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=7vd52um8d9.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=rael@zopyra.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.