All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Luc Herren <jlh@gmx.ch>
To: Git Mailing List <git@vger.kernel.org>
Subject: [PATCH] Documentation: Fix typo
Date: Thu, 31 Jan 2008 03:06:04 +0100	[thread overview]
Message-ID: <47A12D0C.7030304@gmx.ch> (raw)
In-Reply-To: <87myqoxvzk.fsf@rho.meyering.net>


Signed-off-by: Jean-Luc Herren <jlh@gmx.ch>
---

Beside the obvious s/if/is/ typo, is it easier to read this way?
It might be my ears but "is run" sounds strange to me.

jlh

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

diff --git a/Documentation/git-cvsserver.txt b/Documentation/git-cvsserver.txt
index c831548..d3e9993 100644
--- a/Documentation/git-cvsserver.txt
+++ b/Documentation/git-cvsserver.txt
@@ -183,7 +183,7 @@ access method and requested operation.
 That means that even if you offer only read access (e.g. by using
 the pserver method), git-cvsserver should have write access to
 the database to work reliably (otherwise you need to make sure
-that the database if up-to-date all the time git-cvsserver is run).
+that the database is up-to-date any time git-cvsserver is executed).
 
 By default it uses SQLite databases in the git directory, named
 `gitcvs.<module_name>.sqlite`. Note that the SQLite backend creates
-- 
1.5.3.8

  parent reply	other threads:[~2008-01-31  2:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 19:38 [PATCH] fix doc typos Jim Meyering
2008-01-30 20:43 ` Miklos Vajna
2008-01-30 20:56   ` Jim Meyering
2008-01-31 19:55     ` [PATCH] git rev-parse manpage: spelling fix Miklos Vajna
2008-01-31  2:06 ` Jean-Luc Herren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-15  8:55 [PATCH] Documentation: fix typo Juergen Borleis
2015-06-16 13:59 ` Sascha Hauer
2022-11-13 12:48 Vlad-Stefan Harbuz
2022-11-14 23:15 ` Taylor Blau

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=47A12D0C.7030304@gmx.ch \
    --to=jlh@gmx.ch \
    --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.