git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francis Daly <francis@daoine.org>
To: git@vger.kernel.org
Subject: [PATCH] avoid asciidoc warning in git-cvsserver.txt
Date: Sun, 5 Mar 2006 11:41:33 +0000	[thread overview]
Message-ID: <20060305114133.GA20399@craic.sysops.org> (raw)


Manually renumber to keep asciidoc happy

---

 Documentation/git-cvsserver.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

9809de6594b8e11261ca5f18bb2eadb913fb33ae
diff --git a/Documentation/git-cvsserver.txt b/Documentation/git-cvsserver.txt
index 19c9c51..0c4948d 100644
--- a/Documentation/git-cvsserver.txt
+++ b/Documentation/git-cvsserver.txt
@@ -44,13 +44,13 @@ INSTALLATION
    n.b. you need to ensure each user that is going to invoke server.pl has
    write access to the log file.
 
-5. On each client machine you need to set the following variables.
+3. On each client machine you need to set the following variables.
      CVSROOT should be set as per normal, but the directory should point at the
              appropriate git repo.
      CVS_SERVER should be set to the server.pl script that has been put on the
                 remote machine.
 
-6. Clients should now be able to check out modules (where modules are the names
+4. Clients should now be able to check out modules (where modules are the names
    of branches in git).
      $ cvs co -d mylocaldir master
 
-- 
1.2.GIT

-- 
Francis Daly        francis@daoine.org

             reply	other threads:[~2006-03-05 11:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-05 11:41 Francis Daly [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-05 12:11 [PATCH] avoid asciidoc warning in git-cvsserver.txt Francis Daly
2006-03-05 19:22 ` Martin Langhoff

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=20060305114133.GA20399@craic.sysops.org \
    --to=francis@daoine.org \
    --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 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).