Re: Confusing git log --- First time bug submission please advise on best practices

From: Francis Stephens <francisstephens@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: Vincent van Ravesteijn <vfr@lyx.org>, git@vger.kernel.org
Subject: Re: Confusing git log --- First time bug submission please advise on best practices
Date: Fri, 7 Feb 2014 09:43:46 +0000	[thread overview]
Message-ID: <CAJaBJzKy0b8MBuB_X_4n8E2=q=CyrpxOyFFrgv_2CQ19pkNmwQ@mail.gmail.com> (raw)
In-Reply-To: <874n4cjk83.fsf@fencepost.gnu.org>

Thanks for your clear response. I can see where I went wrong now.

On Thu, Feb 6, 2014 at 4:10 PM, David Kastrup <dak@gnu.org> wrote:
> Vincent van Ravesteijn <vfr@lyx.org> writes:
>
>> The commits that are in the log for master and which are not in the
>> log for originssh/master are merged in at "6833fd4 (HEAD, master);
>> Completed merge".
>>
>> As "git log" can only present the commits in a linear way, it shows
>> the commits from the ancentry of both parents of HEAD in a reverse
>> chronological order. This means that the commits from the two
>> ancestries are mixed and commits that are shown after each other don't
>> have to be parent and child. See the documentation of "git log" and
>> the section "Commit Ordering": "By default, the commits are shown in
>> reverse chronological order."
>
> git log --graph can help with getting a better picture.
>
> --
> David Kastrup