git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Benoit Sigoure <tsuna@lrde.epita.fr>
Cc: Steffen Prohaska <prohaska@zib.de>,
	gitster@pobox.com, Ralf.Wildenhues@gmx.de, git@vger.kernel.org
Subject: Re: [PATCH v2] user-manual: add advanced topic "bisecting merges"
Date: Wed, 7 Nov 2007 17:26:49 -0500	[thread overview]
Message-ID: <20071107222649.GL29728@fieldses.org> (raw)
In-Reply-To: <F783880C-A0F9-45D9-A23A-075600B31CEE@lrde.epita.fr>

On Wed, Nov 07, 2007 at 11:16:06PM +0100, Benoit Sigoure wrote:
> Hi Steffen,
>
> On Nov 7, 2007, at 10:50 PM, Steffen Prohaska wrote:
>
>> This commits adds a discussion of the challenge of bisecting
>> merge commits to the user manual. The text is slightly
>> adapted from a mail by Junio C Hamano <gitster@pobox.com>
>> to the mailing list
>> <http://marc.info/?l=git&m=119403257315527&w=2>.
>>
>> The discussion is added to "Exploring git history" in a
>> sub-section titled "Advanced topics". The discussion requires
>> detailed knowledge about git. It is assumed that the reader will
>> skip advanced topics on first reading. At least the text suggest
>> to do so.
>>
>> Signed-off-by: Steffen Prohaska <prohaska@zib.de>
>> ---
>>  Documentation/user-manual.txt |   89 
>> +++++++++++++++++++++++++++++++++++++++++
>>  1 files changed, 89 insertions(+), 0 deletions(-)
>>
>> Some minor errors were fixed. Thanks to <Ralf.Wildenhues@gmx.de>.
>>
>> I kept the naming of the commits. Benoit Sigoure suggested to choose
>> a different naming which he claims would be easier to remember.
>> I'm not convinced. The current naming starts with X, Y, Z on the left
>> and names the remaining commits on the right with A, B, C, D. This
>> is simple and give sufficient orientation.
>
> I still disagree but...  fair enough ;)
> You end up comparing [ABCD] with [XYZ] which (to me) is hard to follow 
> because it's like you were comparing two different kind of entities.  I 
> tend to think more in term of branch (e.g. what's happened to the upper 
> branch and what's happened to the lower branch, rather than think in terms 
> of "before a point in time" and "after that point in time").  Because of 
> that, I constantly need to look back at the scheme to find out what is `A', 
> what is `Z' etc.
>
> Some more comments below.  Sorry for not spotting these earlier.
>
>>
>> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
>> index d99adc6..d0e738e 100644
>> --- a/Documentation/user-manual.txt
>> +++ b/Documentation/user-manual.txt
>> @@ -934,6 +934,95 @@ Figuring out why this works is left as an exercise to 
>> the (advanced)
>>  student.  The gitlink:git-log[1], gitlink:git-diff-tree[1], and
>>  gitlink:git-hash-object[1] man pages may prove helpful.
>>
>> +[[history-advanced-topics]]
>> +Advanced topics
>> +---------------
>> +This section covers advanced topics that typically require more
>> +knowledge about git than the manual presented to this point.
>> +
>> +You may want to skip the section at first reading, and come back
>
> I think the correct wording here is "on first reading".  If a native 
> English speaker could confirm this...

Confirmed....

--b.

  reply	other threads:[~2007-11-07 22:27 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 [this message]
2007-11-08  6:40       ` Steffen Prohaska
2007-11-08  7:19     ` Johannes Sixt
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=20071107222649.GL29728@fieldses.org \
    --to=bfields@fieldses.org \
    --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).