From: Christian Couder <chriscool@tuxfamily.org>
To: Jon Seymour <jon.seymour@gmail.com>
Cc: git@vger.kernel.org, j6t@kdbg.org, gitster@pobox.com, jnareb@gmail.com
Subject: Re: [PATCH 0/5] bisect: Add support for a --no-checkout option.
Date: Sat, 30 Jul 2011 15:48:08 +0200 [thread overview]
Message-ID: <201107301548.09815.chriscool@tuxfamily.org> (raw)
In-Reply-To: <1312014511-7157-1-git-send-email-jon.seymour@gmail.com>
Hi,
On Saturday 30 July 2011 10:28:26 Jon Seymour wrote:
> For some bisection tasks, checking out the commit at each stage of the
> bisection process is unecessary or undesirable.
>
> This series adds support for a --no-checkout[=<ref>] option to git-bisect.
Sorry but I didn't reply to your previous email when you asked about a "--no-
checkout[=<ref>]" compromise. I thought that Junio would reply and then I
forgot about it.
My opinion is that if you really want to be able to use another ref, then
there should be a special "--update-ref=<ref>" or "--use-ref=<ref>" option
that is different from "--no-checkout".
"--no-checkout" looks like a boolean argument. And "--no-checkout[=<ref>]" may
make the user think that this option will not checkout <ref>, and then it
leads to the confusing question "but why would it checkout this f&#@ing ref in
the first place?".
Thanks,
Christian.
next prev parent reply other threads:[~2011-07-30 13:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 8:28 [PATCH 0/5] bisect: Add support for a --no-checkout option Jon Seymour
2011-07-30 8:28 ` [PATCH 1/5] bisect: add tests to document expected behaviour in presence of broken trees Jon Seymour
2011-07-30 8:28 ` [PATCH 2/5] bisect: introduce support for --no-checkout=<ref> option Jon Seymour
2011-07-30 13:49 ` Christian Couder
2011-07-30 8:28 ` [PATCH 3/5] bisect: introduce --no-checkout[=<ref>] support into porcelain Jon Seymour
2011-07-30 14:34 ` Christian Couder
2011-07-30 17:00 ` Jon Seymour
2011-07-31 0:36 ` Christian Couder
2011-08-01 0:53 ` Junio C Hamano
2011-08-01 4:35 ` Christian Couder
2011-07-30 8:28 ` [PATCH 4/5] bisect: add tests for the --no-checkout option Jon Seymour
2011-07-30 8:28 ` [PATCH 5/5] bisect: add documentation for --no-checkout[=<ref>] option Jon Seymour
2011-07-30 8:30 ` [PATCH 0/5] bisect: Add support for a --no-checkout option Jon Seymour
2011-07-30 13:48 ` Christian Couder [this message]
2011-07-30 13:58 ` Jon Seymour
2011-07-30 14:19 ` Christian Couder
2011-08-01 1:00 ` Junio C Hamano
2011-08-01 4:42 ` Christian Couder
2011-08-01 5:27 ` Jon Seymour
2011-08-01 17:33 ` Junio C Hamano
2011-08-01 22:19 ` Jon Seymour
2011-08-01 23:33 ` Junio C Hamano
2011-08-02 1:15 ` Jon Seymour
2011-08-02 1:41 ` Jon Seymour
2011-08-02 17:53 ` Junio C Hamano
2011-08-02 21:27 ` Jon Seymour
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=201107301548.09815.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jnareb@gmail.com \
--cc=jon.seymour@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).