From: Mukund <muks@mukund.org>
To: git@vger.kernel.org
Subject: [PATCH] Fixed some typos in git-repack docs
Date: Sat, 10 Feb 2007 23:42:01 +0530 [thread overview]
Message-ID: <45CE0AF1.50101@mukund.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
---
Documentation/git-repack.txt | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-repack.txt b/Documentation/git-repack.txt
index 4a57ce8..d39abc1 100644
--- a/Documentation/git-repack.txt
+++ b/Documentation/git-repack.txt
@@ -30,9 +30,9 @@ OPTIONS
Instead of incrementally packing the unpacked objects,
pack everything available into a single pack.
Especially useful when packing a repository that is used
- for a private development and there no need to worry
- about people fetching via dumb protocols from it. Use
- with '-d'.
+ for private development and there is no need to worry
+ about people fetching via dumb file transfer protocols
+ from it. Use with '-d'.
-d::
After packing, if the newly created packs make some
--
1.4.4.2
--
Banu -- Free software for science, media and graphics
http://www.banu.com/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 855 bytes --]
reply other threads:[~2007-02-10 19:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45CE0AF1.50101@mukund.org \
--to=muks@mukund.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).