From: Jakub Narebski <jnareb@gmail.com>
To: "Tajti Ákos" <akos.tajti@intland.com>
Cc: git@vger.kernel.org
Subject: Re: listing changesets on a branch
Date: Tue, 26 Jul 2011 04:46:17 -0700 (PDT) [thread overview]
Message-ID: <m38vrls1sy.fsf@localhost.localdomain> (raw)
In-Reply-To: <4E2E9676.5000307@intland.com>
Tajti Ákos <akos.tajti@intland.com> writes:
> I'd like to list the changesets between two commit ids, but only
> those, that were committed on a specific branch. I tried to use the
> following command:
>
> git log --branches=*/master rev1..rev2
>
> But the result is not what I expected: i see sommits that were made on
> an other branch and were not merged to master. Could you please tell
> me what I am doing wrong?
In Git there isn't such thing like "commits made on a specific branch".
Branches are simply references to DAG, and "on branch" means commits
reachable from branch tip (branch head).
Anyway, try `--ancestry-path` option (in git-log(1) manpage), which
make Git show only those commits that are on line joining rev2 to
rev1. I guess it is what you really want.
HTH
--
Jakub Narębski
prev parent reply other threads:[~2011-07-26 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 10:27 listing changesets on a branch Tajti Ákos
2011-07-26 11:46 ` Jakub Narebski [this message]
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=m38vrls1sy.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=akos.tajti@intland.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).