From: Steve Haslam <shaslam@lastminute.com>
To: git@vger.kernel.org
Cc: Steve Haslam <shaslam@lastminute.com>
Subject: [PATCH] Remove references to git-fetch-pack from "git clone" documentation.
Date: Fri, 25 Jul 2008 19:37:48 +0100 [thread overview]
Message-ID: <1217011068-1675-1-git-send-email-shaslam@lastminute.com> (raw)
"git clone" no longer calls "git-fetch-pack", so the documentation is a bit
stale. Instead, state that the -u option is to be used when accessing a
repository over ssh.
Signed-off-by: Steve Haslam <shaslam@lastminute.com>
---
This is somewhat related to a patch I just sent; typically I forgot
about the documentation until after sending it.
Documentation/git-clone.txt | 9 ++++-----
1 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 91efac9..26fd1b1 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -87,8 +87,8 @@ then the cloned repository will become corrupt.
--quiet::
-q::
- Operate quietly. This flag is passed to "rsync" and
- 'git-fetch-pack' commands when given.
+ Operate quietly. This flag is also passed to the `rsync'
+ command when given.
--no-checkout::
-n::
@@ -113,9 +113,8 @@ then the cloned repository will become corrupt.
--upload-pack <upload-pack>::
-u <upload-pack>::
- When given, and the repository to clone from is handled
- by 'git-fetch-pack', `--exec=<upload-pack>` is passed to
- the command to specify non-default path for the command
+ When given, and the repository to clone from is accessed
+ via ssh, this specifies a non-default path for the command
run on the other end.
--template=<template_directory>::
--
1.6.0.rc0.43.g1cd6
next reply other threads:[~2008-07-25 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 18:37 Steve Haslam [this message]
2008-07-26 3:24 ` [PATCH] Remove references to git-fetch-pack from "git clone" documentation Johannes Schindelin
2008-07-28 12:32 ` Steve Haslam
2008-07-28 12:41 ` Johannes Schindelin
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=1217011068-1675-1-git-send-email-shaslam@lastminute.com \
--to=shaslam@lastminute.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 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).