From: Christian Couder <chriscool@tuxfamily.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Pierre Habouzit <madcoder@debian.org>,
Alexey Zaytsev <alexey.zaytsev@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: current git kernel has strange problems during bisect
Date: Mon, 12 Jan 2009 06:03:03 +0100 [thread overview]
Message-ID: <200901120603.03977.chriscool@tuxfamily.org> (raw)
In-Reply-To: <200901120551.56791.chriscool@tuxfamily.org>
I wrote:
>
> Anyway it looks to me that this kind of problem could be avoided if one
> could "replace" some commits only when bisecting. In this case what could
> be done is that one could "replace" the commit where btrfs is merged with
> one commit that cuts off the btrfs history.
By the way, it possible right now to cut off the btrfs history in one's own
repository using a graft. One don't need to wait for me to finish the
replace stuff I am slowly working on. But on the other hand it will have
all the restrictions of the current graft mechanism.
Regards,
Christian.
next prev parent reply other threads:[~2009-01-12 5:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 15:02 current git kernel has strange problems during bisect Christian Borntraeger
2009-01-11 15:07 ` Christian Borntraeger
2009-01-11 15:14 ` Johannes Schindelin
2009-01-11 15:20 ` Christian Borntraeger
2009-01-11 16:31 ` Boaz Harrosh
2009-01-11 19:13 ` Linus Torvalds
2009-01-11 19:42 ` Sam Ravnborg
2009-01-11 19:47 ` Alexey Zaytsev
2009-01-11 23:02 ` Pierre Habouzit
2009-01-12 4:51 ` Christian Couder
2009-01-12 5:03 ` Christian Couder [this message]
2009-01-11 20:04 ` Linus Torvalds
2009-01-11 21:39 ` Christian Borntraeger
2009-01-11 22:27 ` Daniel Barkalow
2009-01-13 20:26 ` Kyle Moffett
2009-01-15 16:54 ` Andreas Bombe
2009-01-15 23:13 ` Kyle Moffett
2009-01-11 21:54 ` Sam Ravnborg
2009-01-11 22:17 ` Alexey Zaytsev
2009-01-11 22:32 ` Sam Ravnborg
2009-01-11 22:34 ` Daniel Barkalow
2009-01-11 20:29 ` Andi Kleen
2009-01-11 20:51 ` 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=200901120603.03977.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=alexey.zaytsev@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madcoder@debian.org \
--cc=sam@ravnborg.org \
--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).