From: Mike Hommey <mh@glandium.org>
To: git@vger.kernel.org
Subject: Walking children commits?
Date: Tue, 31 Mar 2015 08:02:09 +0900 [thread overview]
Message-ID: <20150330230209.GA20421@glandium.org> (raw)
Hi,
I am trying to get all the children commits of a set of commits. To do
that, I'm using this:
git rev-list --topo-order --ancestry-path --boundary <all heads> ^A ^B ...
where A, B, and following are those commits I want the children of. From
the gitrevisions documentation, it seems that should get me what I want,
but if I build a dag manually (from the output of rev-list --parents)
and get all the children of those commits, I get more results than what
the command above returns (and that command also gives false positives).
Am I doing something wrong, or am I hitting a bug in --ancestry-path
walking? In the latter case, I'll try to find a reduced test case,
because currently, this involves a 260k commit, 1.5GB repository with
close to 2k heads and a set of 153 commits to find the children of.
Cheers,
Mike
next reply other threads:[~2015-03-30 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 23:02 Mike Hommey [this message]
2015-03-30 23:35 ` Walking children commits? Mike Hommey
2015-03-30 23:44 ` Mike Hommey
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=20150330230209.GA20421@glandium.org \
--to=mh@glandium.org \
--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).