Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> 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.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html