From: Peter Hagervall Date: Fri, 16 Sep 2005 14:24:12 GMT Subject: Re: PATCH Documentation/git-rev-list.txt typo fix Message-ID: <20050916142412.GA973@brainysmurf.cs.umu.se> In-Reply-To: On Thu, Sep 15, 2005 at 05:40:13PM -0500, jdl@freescale.com wrote: > I'm not positive what the doc conventions are, but I think > something like this patch fixes the "superscript" problem > on the git-rev-list doc page. > > Signed-off-by: Jon Loeliger > -if "git-rev-list --bisect foo ^bar ^baz" outputs 'midpoint', the output > -of "git-rev-list foo ^midpoint" and "git-rev-list midpoint ^bar ^baz" > +if 'git-rev-list --bisect foo ^bar ^baz' outputs 'midpoint', the output > +of 'git-rev-list foo ^midpoint' and 'git-rev-list midpoint ^bar ^baz' This causes a mismatch in and tags, one way of fixing it is having no more than one caret symbol per line, which is the only solution I found in the asciidoc documentation. Ugly, but it works. Signed-off-by: Peter Hagervall --- diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt --- a/Documentation/git-rev-list.txt +++ b/Documentation/git-rev-list.txt @@ -32,8 +32,11 @@ I have the commit object 'bar', but not The *--bisect* flag limits output to the one commit object which is roughly halfway between the included and excluded commits. Thus, -if 'git-rev-list --bisect foo ^bar ^baz' outputs 'midpoint', the output -of 'git-rev-list foo ^midpoint' and 'git-rev-list midpoint ^bar ^baz' +if 'git-rev-list --bisect foo ^bar +^baz' outputs 'midpoint', the output +of 'git-rev-list foo ^midpoint' and 'git-rev-list midpoint +^bar +^baz' would be of roughly the same length. Finding the change which introduces a regression is thus reduced to a binary search: repeatedly generate and test new 'midpoint's until the commit chain is of length one.