From: Jonathan Nieder <jrnieder@gmail.com>
To: Frans Pop <elendil@planet.nl>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Testing if a certain commit is in the current branch
Date: Wed, 27 Jan 2010 04:19:43 -0600 [thread overview]
Message-ID: <20100127101943.GA4470@progeny.tock> (raw)
In-Reply-To: <201001270936.14935.elendil@planet.nl>
Frans Pop wrote:
> The use case is a wrapper script for kernel builds in which some variation
> are needed (due to changes in the build system) when building older
> kernels, e.g. during bisections or when building older stable updates.
> So I test for the presence of commits that introduced relevant changes.
Neat idea. How about this (untested)?
git rev-list ^HEAD --no-walk commit1 commit2 ...
next prev parent reply other threads:[~2010-01-27 10:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 7:19 Testing if a certain commit is in the current branch Frans Pop
2010-01-27 7:24 ` Junio C Hamano
2010-01-27 8:36 ` Frans Pop
2010-01-27 10:19 ` Jonathan Nieder [this message]
2010-01-27 13:26 ` Frans Pop
2010-01-27 15:15 ` Dale Farnsworth
2010-01-27 15:39 ` Frans Pop
2010-01-27 15:08 ` Petr Baudis
2010-01-27 15:27 ` Frans Pop
2010-01-27 8:26 ` Matthieu Moy
2010-01-27 8:47 ` Frans Pop
2010-01-27 8:56 ` Johannes Schindelin
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=20100127101943.GA4470@progeny.tock \
--to=jrnieder@gmail.com \
--cc=elendil@planet.nl \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).