All of lore.kernel.org
 help / color / mirror / Atom feed
From: jdl@freescale.com
To: git@vger.kernel.org
Subject: PATCH Documentation/git-rev-list.txt typo fix
Date: Thu, 15 Sep 2005 17:40:13 -0500	[thread overview]
Message-ID: <E1EG2Or-0005E2-Pw@jdl.com> (raw)

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 <jdl@freescale.com>
---


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,8 @@ 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.

             reply	other threads:[~2005-09-15 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15 22:40 jdl [this message]
2005-09-16 14:24 ` PATCH Documentation/git-rev-list.txt typo fix Peter Hagervall
2005-09-16 16:31   ` Junio C Hamano
2005-09-16 20:02     ` Chris Wright
2005-09-16 20:06       ` Chris Wright
2005-09-16 20:47         ` jdl
2005-09-16 23:01   ` Junio C Hamano

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=E1EG2Or-0005E2-Pw@jdl.com \
    --to=jdl@freescale.com \
    --cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.