From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Could this be done simpler?
Date: Fri, 26 Jun 2009 00:55:23 +0200 [thread overview]
Message-ID: <200906260055.23929.chriscool@tuxfamily.org> (raw)
In-Reply-To: <7vprcsymjd.fsf@alter.siamese.dyndns.org>
On Friday 26 June 2009, Junio C Hamano wrote:
> Christian Couder <chriscool@tuxfamily.org> writes:
> >> If someone creates a "git decompose-octopus <commit>" command then ...
>
> I am afraid that misses the entire point of my discussion.
>
> Such a decomposed octopus would _only_ be necessary during bisection,
> only when the user chooses to test two tips at once (instead of testing
> one by one), _and_ only its tree is needed for that purpose. In other
> words, we should be able to do this _without_ creating an extra commit,
> let alone replace mechanism.
But suppose the result from the bisection tells that M1 is the first bad
commit, then the user will need to look at M1, and perhaps check it out or
use it in other ways after the bisection is finished. So why shouldn't it
be a real commit?
It's not like a few more commits are a big problem as they will be reclaimed
by garbage collection anyway if the replace ref is deleted.
Best regards,
Christian.
prev parent reply other threads:[~2009-06-25 22:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 21:35 Could this be done simpler? Linus Torvalds
2009-06-25 1:04 ` Junio C Hamano
2009-06-25 14:33 ` Randal L. Schwartz
2009-06-25 16:32 ` Matthias Andree
2009-06-25 17:25 ` Junio C Hamano
2009-06-25 21:54 ` Matthias Andree
2009-06-27 0:26 ` Junio C Hamano
2009-06-25 18:32 ` Junio C Hamano
2009-06-25 17:19 ` Michael J Gruber
2009-06-25 22:02 ` Christian Couder
2009-06-25 22:23 ` Christian Couder
2009-06-25 22:29 ` Junio C Hamano
2009-06-25 22:50 ` Linus Torvalds
2009-06-25 23:17 ` Junio C Hamano
2009-06-25 22:55 ` Christian Couder [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=200906260055.23929.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.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).