From: "Bryan O'Sullivan" <bryano@fb.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: logging disjoint sets of commits in a single command
Date: Wed, 1 Feb 2012 00:27:06 +0000 [thread overview]
Message-ID: <CB4DC442.72F%bryano@fb.com> (raw)
In-Reply-To: <CB4DC432.72D%bryano@fb.com>
On 2012-01-31 16:15 , "Bryan O'Sullivan" <bryano@fb.com> wrote:
>I'm trying to use "git log" to display only a handful of commits, where
>the commits are not necessarily linearly related to each other.
And I beautifully fat-fingered the "send" key. Oops.
What I was *going* to say was that it looks like revision.c:limit_list is
(whether intentionally or not) getting in the way of this.
Here's a sample command line against a kernel tree:
git log 373af0c^..373af0c 590dfe2^..590dfe2
I want git to log those two specific commits, but in fact it looks like
limit_list is marking 590dfe2 as UNINTERESTING while processing 373af0c,
and so it gets pruned.
Is there some way around this, or would a patch to fix it be acceptable?
next prev parent reply other threads:[~2012-02-01 0:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 0:15 logging disjoint sets of commits in a single command Bryan O'Sullivan
2012-02-01 0:27 ` Bryan O'Sullivan [this message]
2012-02-01 0:39 ` Carlos Martín Nieto
2012-02-01 0:53 ` Jeff King
2012-02-01 1:02 ` Bryan O'Sullivan
2012-02-01 3:03 ` Jeff King
2012-02-01 22:01 ` Bryan O'Sullivan
2012-02-01 0:48 ` 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=CB4DC442.72F%bryano@fb.com \
--to=bryano@fb.com \
--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).