From: Johannes Sixt <j.sixt@viscovery.net>
To: Steffen Prohaska <prohaska@zib.de>
Cc: gitster@pobox.com, Ralf.Wildenhues@gmx.de, tsuna@lrde.epita.fr,
git@vger.kernel.org
Subject: Re: [PATCH v2] user-manual: add advanced topic "bisecting merges"
Date: Thu, 08 Nov 2007 08:19:53 +0100 [thread overview]
Message-ID: <4732B899.6000908@viscovery.net> (raw)
In-Reply-To: <11944722214046-git-send-email-prohaska@zib.de>
Steffen Prohaska schrieb:
> +If you linearize the history by rebasing the lower branch on
> +top of the upper, instead of merging, the bug becomes much easier to
> +find and understand. Your history would instead be:
At this point I'm missing the words
The solution is ...
I.e.:
The solution is to linearize the history by rebasing the lower branch on
top of the upper, instead of merging. Now the bug becomes much easier to
find and understand. Your history would instead be:
-- Hannes
next prev parent reply other threads:[~2007-11-08 7:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 9:16 [PATCH] user-manual: add advanced topic "bisecting merges" Steffen Prohaska
2007-11-04 11:23 ` Ralf Wildenhues
2007-11-07 21:50 ` [PATCH v2] " Steffen Prohaska
2007-11-07 22:16 ` Benoit Sigoure
2007-11-07 22:26 ` J. Bruce Fields
2007-11-08 6:40 ` Steffen Prohaska
2007-11-08 7:19 ` Johannes Sixt [this message]
2007-11-08 8:59 ` Steffen Prohaska
2007-11-08 9:11 ` Johannes Sixt
2007-11-08 9:33 ` Andreas Ericsson
2007-11-08 9:53 ` Johannes Sixt
2007-11-08 12:54 ` Steffen Prohaska
2007-11-08 13:22 ` Johannes Sixt
2007-11-08 14:55 ` Steffen Prohaska
2007-11-10 9:48 ` [PATCH v3] " Steffen Prohaska
2007-11-10 10:36 ` Junio C Hamano
2007-11-10 11:16 ` Steffen Prohaska
2007-11-10 13:49 ` [PATCH v4] user-manual: Add section "Why bisecting merge commits can be harder ..." Steffen Prohaska
2007-11-10 19:10 ` Linus Torvalds
2007-11-10 20:25 ` Junio C Hamano
2007-11-10 22:41 ` Steffen Prohaska
2007-11-18 3:59 ` J. Bruce Fields
2007-11-18 9:47 ` Steffen Prohaska
2007-11-18 23:18 ` J. Bruce Fields
2007-11-08 13:38 ` [PATCH v2] user-manual: add advanced topic "bisecting merges" Andreas Ericsson
2007-11-08 14:51 ` Benoit Sigoure
2007-11-08 15:07 ` Steffen Prohaska
2007-11-08 15:23 ` Johannes Schindelin
2007-11-08 18:38 ` Brian Gernhardt
2007-11-04 13:50 ` [PATCH] " Benoit SIGOURE
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=4732B899.6000908@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=Ralf.Wildenhues@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=prohaska@zib.de \
--cc=tsuna@lrde.epita.fr \
/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).