From: Jeff King <peff@peff.net>
To: Chris Packham <judge.packham@gmail.com>
Cc: GIT <git@vger.kernel.org>
Subject: Re: Getting a list of commits between 2 points without upstream changes
Date: Sun, 17 Jul 2011 20:17:49 -0400 [thread overview]
Message-ID: <20110718001749.GA706@sigill.intra.peff.net> (raw)
In-Reply-To: <CAFOYHZC5hQ9JV8a5d20AaPR_eYFDViama+4148MPumvvJ-n6wQ@mail.gmail.com>
On Mon, Jul 18, 2011 at 11:49:57AM +1200, Chris Packham wrote:
> I'm trying to send round an incremental changelog for my project which
> contains just my changes without changes that have been made upstream.
> The history look something like this.
>
> ---o--o--o--o--o--o--o--o-- upstream
> \ \ \
> \-m--A--m--B--m--C--D-- topic
>
> What I want is a changelog with just B, C and D in it (i.e. no merge
> commits and no commits already in upstream). I know if I wanted A,B,C
> and D I could just do 'git log --no-merges upstream..topic'. If I do
> 'git log --no-merges B..topic' I get the merged commits from upstream.
> In set-speak what I think want is the union of upstream..topic and
> B..topic.
I'm not clear on what makes "B" more special than "A" in the graph
above. But assuming you know A, don't you just want:
git log --no-merges topic ^upstream ^A
? That is, "everything in topic, but not in upstream, nor in the parent
of A". Or if you know A and not B, you can use "^B^!" (which means "do
not include commits that are in any parent of B").
-Peff
next prev parent reply other threads:[~2011-07-18 0:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 23:49 Getting a list of commits between 2 points without upstream changes Chris Packham
2011-07-18 0:17 ` Jeff King [this message]
2011-07-18 0:33 ` Chris Packham
2011-07-18 1:28 ` Jeff King
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=20110718001749.GA706@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=judge.packham@gmail.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 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).