From: Junio C Hamano <gitster@pobox.com>
To: Philippe De Muyter <phdm@macq.eu>
Cc: git@vger.kernel.org
Subject: Re: identical hashes on two branches, but holes in git log
Date: Tue, 19 May 2015 09:01:10 -0700 [thread overview]
Message-ID: <xmqq617oa75l.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150519132958.GA21130@frolo.macqel> (Philippe De Muyter's message of "Tue, 19 May 2015 15:29:58 +0200")
Philippe De Muyter <phdm@macq.eu> writes:
> Trying to understand, I have eventually done "git log" on my branch and
> on v3.15 with the following commands :
>
> git log v3.15 --full-history --decorate=short | grep '^commit' > /tmp/3.15.commits
> git log --full-history --decorate=short | grep '^commit' > /tmp/mybranch.commits
Either
git log --oneline v3.15..HEAD ;# show what I have not in theirs
or
gitk v3.15...HEAD ;# show our differences graphically
may give you a better picture than what you did, which was to
artificially flatten the topology and lose the crucial information
as to which commit is the parents of which other commit.
next prev parent reply other threads:[~2015-05-19 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 13:29 identical hashes on two branches, but holes in git log Philippe De Muyter
2015-05-19 16:01 ` Junio C Hamano [this message]
2015-05-19 21:47 ` Philippe De Muyter
2015-05-19 22:12 ` Junio C Hamano
2015-05-21 7:15 ` Philippe De Muyter
2015-05-21 19:58 ` Philip Oakley
2015-05-21 20:37 ` Philippe De Muyter
2015-05-20 7:39 ` Christian Couder
2015-05-19 23:39 ` Jeff King
2015-05-20 13:13 ` Philippe De Muyter
2015-05-20 13:25 ` John Keeping
2015-05-20 14:12 ` Philippe De Muyter
2015-05-20 16:18 ` Jeff King
2015-05-21 7:05 ` Philippe De Muyter
2015-05-21 16:45 ` Junio C Hamano
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=xmqq617oa75l.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=phdm@macq.eu \
/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.