From: Jon Seymour <jon.seymour@gmail.com>
To: git@vger.kernel.org
Cc: chriscool@tuxfamily.org, gitster@pobox.com, j6t@kdbg.org,
jnareb@gmail.com, Jon Seymour <jon.seymour@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: [PATCH v8 0/7] bisect: Add support for --no-checkout and --update-ref=<ref> options.
Date: Sun, 31 Jul 2011 23:26:18 +1000 [thread overview]
Message-ID: <CAH3AnroWm-BU1svjJqK3WzoNknWk495AJ0mxwWMq+1sgAxxnPg@mail.gmail.com> (raw)
In-Reply-To: <1312113321-28760-1-git-send-email-jon.seymour@gmail.com>
On Sun, Jul 31, 2011 at 9:55 PM, Jon Seymour <jon.seymour@gmail.com> wrote:
>
> For example:
>
> git bisect run eval '
> rc=1;
> if git rev-list --objects HEAD >tmp.$$; then
> git pack-objects --stdout >/dev/null < tmp.$$ && rc=0;
> fi;
> rm tmp.$$;
> test $rc -eq 0;'
>
Sverre has pointed out I screwed the example up again. It should have been:
git bisect start HEAD <some-known-good-commit> <boundary-commits> --no-checkout
git bisect run eval '
rc=1;
if git rev-list --objects HEAD >tmp.$$; then
git pack-objects --stdout >/dev/null < tmp.$$ && rc=0;
fi;
rm tmp.$$;
test $rc -eq 0;'
I think the examples in the documentation and test are correct (modulo
an accurate description of what good choices for <boundary-commit>'s
are).
jon.
prev parent reply other threads:[~2011-07-31 13:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 11:55 [PATCH v8 0/7] bisect: Add support for --no-checkout and --update-ref=<ref> options Jon Seymour
2011-07-31 11:55 ` [PATCH v8 1/7] bisect: move argument parsing before state modification Jon Seymour
2011-07-31 11:55 ` [PATCH v8 2/7] bisect: add tests to document expected behaviour in presence of broken trees Jon Seymour
2011-07-31 11:55 ` [PATCH v8 3/7] bisect: introduce support for --update-ref=<ref> option Jon Seymour
2011-07-31 11:55 ` [PATCH v8 4/7] bisect: introduce --no-checkout, --update-ref=<ref> support into porcelain Jon Seymour
2011-07-31 18:35 ` Christian Couder
2011-07-31 19:48 ` Jon Seymour
2011-07-31 20:05 ` Christian Couder
2011-07-31 19:21 ` Christian Couder
2011-07-31 19:40 ` Jon Seymour
2011-07-31 20:07 ` Christian Couder
2011-07-31 20:51 ` Christian Couder
2011-07-31 21:11 ` Jon Seymour
2011-07-31 11:55 ` [PATCH v8 5/7] bisect: add tests for the --no-checkout and --update-ref options Jon Seymour
2011-07-31 11:55 ` [PATCH v8 6/7] bisect: add documentation for --no-checkout and --update-ref=<ref> options Jon Seymour
2011-07-31 11:55 ` [PATCH v8 7/7] bisect: support --update-ref <ref> Jon Seymour
2011-07-31 13:26 ` Jon Seymour [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=CAH3AnroWm-BU1svjJqK3WzoNknWk495AJ0mxwWMq+1sgAxxnPg@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jnareb@gmail.com \
--cc=srabbelier@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).