From: Artur Skawina <art.08.09@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: Determining commit reachability
Date: Sun, 05 Sep 2010 22:34:11 +0200 [thread overview]
Message-ID: <4C83FEC3.3040101@gmail.com> (raw)
Given commit C, refs (branches) R, S and T what would be the best way
to test whether 'C' is reachable from any of the heads?
Checking if `git rev-list -n1 O ^R ^S ^T` produces any output is what
i came up with; is there a better (ie faster) solution?
artur
next reply other threads:[~2010-09-05 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 20:34 Artur Skawina [this message]
2010-09-06 3:17 ` Determining commit reachability Jeff King
2010-09-06 5:04 ` Artur Skawina
2010-09-06 6:47 ` Junio C Hamano
2010-09-06 20:45 ` Sverre Rabbelier
2010-09-06 20:53 ` Ævar Arnfjörð Bjarmason
2010-09-06 21:05 ` Sverre Rabbelier
2010-09-06 23:38 ` Junio C Hamano
2010-09-07 5:52 ` [PATCH] Documentation: explain "git branch --with" Jonathan Nieder
2010-09-07 10:51 ` Ævar Arnfjörð Bjarmason
2010-09-09 22:45 ` Junio C Hamano
2010-09-07 13:04 ` Determining commit reachability Nguyen Thai Ngoc Duy
2010-09-07 13:07 ` Nguyen Thai Ngoc Duy
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=4C83FEC3.3040101@gmail.com \
--to=art.08.09@gmail.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).