From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jon Seymour <jon.seymour@gmail.com>,
git@vger.kernel.org, j6t@kdbg.org, jnareb@gmail.com
Subject: Re: [PATCH v14 5/8] bisect: introduce --no-checkout support into porcelain.
Date: Wed, 3 Aug 2011 07:28:42 +0200 [thread overview]
Message-ID: <201108030728.42453.chriscool@tuxfamily.org> (raw)
In-Reply-To: <7vk4avcsk9.fsf@alter.siamese.dyndns.org>
On Wednesday 03 August 2011 01:16:54 Junio C Hamano wrote:
>
> Having said that, other than these minor nits, I think this round is
> almost ready. I didn't check how it behaves upon "bisect reset",
> though. It shouldn't touch the index, HEAD nor the working tree (it
> probably is just the matter of "update-ref -d BISECT_HEAD" and nothing
> else, but I haven't thought things through thoroughly).
>
> Further polishing we may want to do while it is still in pu/next I can
> think of off the top of my head are:
>
> - In this mode, I can bisect the history even inside a bare repository,
> as the whole point of --no-checkout is that the mode does not require a
> working tree. I however suspect "git bisect" requires working tree. Is
> this something we want to fix?
>
> - Further, perhaps should we default to this mode inside a bare
> repository?
I agree that it would be nice if it worked in a bare repo. I did not look at
that yet.
> Christian, do you think of anything else?
No, I agree that it looks almost ready.
The few improvements I would like are:
- squashing the last patch into the previous ones,
- using a bisect_mode() function when needed.
> Also do you see flaws in our
> reasoning that updating only BISECT_HEAD and doing nothing else is a good
> way to do this?
No, I agree that --no-checkout is a good idea and that using only BISECT_HEAD
is good way to do this.
Thanks,
Christian.
next prev parent reply other threads:[~2011-08-03 5:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 22:15 [PATCH v14 0/8] bisect: Add support for --no-checkout option Jon Seymour
2011-08-02 22:15 ` [PATCH v14 1/8] bisect: move argument parsing before state modification Jon Seymour
2011-08-02 22:15 ` [PATCH v14 2/8] bisect: use && to connect statements that are deferred with eval Jon Seymour
2011-08-02 22:15 ` [PATCH v14 3/8] bisect: add tests to document expected behaviour in presence of broken trees Jon Seymour
2011-08-02 22:15 ` [PATCH v14 4/8] bisect: introduce support for --no-checkout option Jon Seymour
2011-08-02 22:15 ` [PATCH v14 5/8] bisect: introduce --no-checkout support into porcelain Jon Seymour
2011-08-02 23:01 ` Junio C Hamano
2011-08-02 23:16 ` Junio C Hamano
2011-08-03 5:28 ` Christian Couder [this message]
2011-08-03 13:16 ` Jon Seymour
2011-08-03 15:24 ` Jon Seymour
2011-08-03 17:01 ` Junio C Hamano
2011-08-03 18:57 ` Jonathan Nieder
2011-08-03 21:40 ` Jon Seymour
2011-08-03 21:45 ` Jonathan Nieder
2011-08-03 5:17 ` Christian Couder
2011-08-02 22:16 ` [PATCH v14 6/8] bisect: add tests for the --no-checkout option Jon Seymour
2011-08-02 22:16 ` [PATCH v14 7/8] bisect: add documentation for " Jon Seymour
2011-08-02 22:16 ` [PATCH v14 8/8] bisect: change bisect function to update BISECT_HEAD, rather than HEAD Jon Seymour
2011-08-03 4:43 ` Christian Couder
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=201108030728.42453.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).