git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: Adam Simpkins <adam@adamsimpkins.net>
Cc: git@vger.kernel.org
Subject: log --graph --first-parent weirdness
Date: Wed, 4 Jun 2008 18:00:42 +0300	[thread overview]
Message-ID: <20080604150042.GA3038@mithlond.arda.local> (raw)

The output of "git log --graph --first-parent" seems weird. Maybe it's
because I don't understand everything but here's an example anyway:


$ git log --graph --pretty=oneline --abbrev-commit --decorate

M   2ba1dba... (refs/heads/master) Merge branch 'topic'
|\  
| * 432e062... (refs/heads/topic) Change from branch 'topic'
* | b762236... Change from branch 'master'
|/  
* d7fb80a... Initial commit


Normal --first-parent prints this:

$ git log --first-parent --pretty=oneline --abbrev-commit

2ba1dba... Merge branch 'topic'
b762236... Change from branch 'master'
d7fb80a... Initial commit


With --graph it goes:

$ git log --graph --first-parent --pretty=oneline --abbrev-commit

M   2ba1dba... Merge branch 'topic'
|\  
* | b762236... Change from branch 'master'
* | d7fb80a... Initial commit
 /


So, it prints the second parent line but it leads to nowhere. Try the
same with the git repository and you'll see a _lots_ of parallel branch
lines which seem to go nowhere.

             reply	other threads:[~2008-06-04 15:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 15:00 Teemu Likonen [this message]
2008-06-04 15:08 ` log --graph --first-parent weirdness Teemu Likonen
2008-06-04 17:12 ` Junio C Hamano
2008-06-04 17:38   ` Teemu Likonen
2008-06-04 18:04     ` Adam Simpkins
2008-06-05  8:56       ` [PATCH] graph API: fix "git log --graph --first-parent" Adam Simpkins
2008-06-04 18:05     ` log --graph --first-parent weirdness Junio C Hamano
2008-06-05  1:37       ` Ping Yin
2008-06-05  9:28       ` Adam Simpkins
2008-06-05  9:50       ` Teemu Likonen
2008-06-05 18:31         ` 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=20080604150042.GA3038@mithlond.arda.local \
    --to=tlikonen@iki.fi \
    --cc=adam@adamsimpkins.net \
    --cc=git@vger.kernel.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 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).