From: しらいしななこ <nanako3@bluebottle.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org
Subject: "git log --first-parent" shows parents that are not first
Date: Sun, 11 May 2008 16:03:20 +0900 [thread overview]
Message-ID: <200805110706.m4B76eLE006432@mi0.bluebottle.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1805 bytes --]
Quoting ãããããªãªã <nanako3@bluebottle.com>:
> The result given by "git log --first-parent" ('next' version) is
> unexpected to me.
>
> % git rev-parse origin/next
> 4eddac518225621c3e4f7285beb879d2b4bad38a
> % git log --abbrev-commit --pretty=oneline --first-parent origin/next^..origin/next
> 4eddac5... Merge branch 'master' into next
> 1f8115b... Merge branch 'maint'
> ca1c991... Merge branch 'sg/merge-options' (early part)
> 31a3c6b... Merge branch 'db/learn-HEAD'
> a064ac1... Merge branch 'jn/webfeed'
> d576c45... Merge branch 'cc/help'
> ca1a5ee... Merge branch 'dm/cherry-pick-s'
> 4c4d3ac... Merge branch 'lt/dirmatch-optim'
> c5445fe... compat-util: avoid macro redefinition warning
> eb120e6... compat/fopen.c: avoid clobbering the system defined fopen macro
> bac59f1... Documentation: bisect: add a few "git bisect run" examples
> d84ae0d... Documentation/config.txt: Add git-gui options
> 921177f... Documentation: improve "add", "pull" and "format-patch" examples
> c904bf3... Be more careful with objects directory permissions on clone
>
> I asked for the log between one commit before the tip of "origin/next" and the tip of the branch, following only the first-parent links. v1.5.5 is not broken and shows the expected result:
>
> % ~/git-v1.5.5/bin/git log --abbrev-commit --pretty=oneline --first-parent origin/next^..origin/next
> 4eddac5... Merge branch 'master' into next
Could you please revert d9c292e8bbd51c84cb9ecd86cb89b8a1b35a2a82? With
that patch reverted from 'next', the problem disappears.
--
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
----------------------------------------------------------------------
Free pop3 email with a spam filter.
http://www.bluebottle.com/tag/5
next reply other threads:[~2008-05-11 7:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 7:03 しらいしななこ [this message]
2008-05-11 18:44 ` "git log --first-parent" shows parents that are not first Junio C Hamano
2008-05-11 23:14 ` [PATCH] revision.c: really honor --first-parent Lars Hjemli
2008-05-12 15:12 ` [PATCH v2] " Lars Hjemli
2008-05-13 20:15 ` Stephen R. van den Berg
2008-05-13 20:43 ` Lars Hjemli
2008-05-13 22:38 ` Junio C Hamano
2008-05-14 10:34 ` Stephen R. van den Berg
2008-05-14 10:54 ` Lars Hjemli
2008-05-14 11:10 ` Stephen R. van den Berg
-- strict thread matches above, loose matches on Subject: below --
2008-05-11 2:23 "git log --first-parent" shows parents that are not first しらいしななこ
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=200805110706.m4B76eLE006432@mi0.bluebottle.com \
--to=nanako3@bluebottle.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.