From: Junio C Hamano <gitster@pobox.com>
To: "W. Trevor King" <wking@tremily.us>
Cc: Git <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] Documentation: Update 'linux-2.6.git' -> 'linux.git'
Date: Wed, 19 Jun 2013 10:07:24 -0700 [thread overview]
Message-ID: <7vtxku112r.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <3286ddfe2dd6cbf9c435bd7f9eb579782eb32e1f.1371606791.git.wking@tremily.us> (W. Trevor King's message of "Tue, 18 Jun 2013 21:55:21 -0400")
"W. Trevor King" <wking@tremily.us> writes:
> diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
> index a0727d7..8e5260f 100644
> --- a/Documentation/git-clone.txt
> +++ b/Documentation/git-clone.txt
> @@ -274,7 +274,7 @@ $ git clone --bare -l /home/proj/.git /pub/scm/proj.git
> * Create a repository on the kernel.org machine that borrows from Linus:
> +
> ------------
> -$ git clone --bare -l -s /pub/scm/.../torvalds/linux-2.6.git \
> +$ git clone --bare -l -s /pub/scm/.../torvalds/linux.git \
> /pub/scm/.../me/subsys-2.6.git
> ------------
Aside from s|subsys-2.6|subsys| David already mentioned, I think
it is a lot saner to remove this particular example. Nobody runs
shell on k.org machines these days, and local borrowing "-l -s" is
already shown in another example.
Also you seem to have missed another "linux-2.6 my2.6" clone in the
first example.
Will not apply in this form; expecting a reroll.
Thanks.
next prev parent reply other threads:[~2013-06-19 17:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 1:55 [PATCH 0/2] Update linux-2.6.git location and repo size W. Trevor King
2013-06-19 1:55 ` [PATCH 1/2] Documentation: Update 'linux-2.6.git' -> 'linux.git' W. Trevor King
2013-06-19 5:05 ` David Aguilar
2013-06-19 11:48 ` W. Trevor King
2013-06-19 19:47 ` W. Trevor King
2013-06-19 21:37 ` Junio C Hamano
2013-06-22 14:46 ` [PATCH v2 0/4] Update linux-2.6.git location and related examples W. Trevor King
2013-06-22 14:46 ` [PATCH v2 1/4] doc/clone: Remove the '--bare -l -s' example W. Trevor King
2013-06-22 14:46 ` [PATCH v2 2/4] doc/clone: Pick more compelling paths for the --reference example W. Trevor King
2013-06-22 14:46 ` [PATCH v2 3/4] Documentation: Update the NFS remote examples to use the staging repo W. Trevor King
2013-06-22 14:46 ` [PATCH v2 4/4] Documentation: Update 'linux-2.6.git' -> 'linux.git' W. Trevor King
2013-06-30 1:05 ` [PATCH v2 0/4] Update linux-2.6.git location and related examples W. Trevor King
2013-06-30 1:44 ` Junio C Hamano
2013-06-30 10:48 ` W. Trevor King
2013-06-19 17:07 ` Junio C Hamano [this message]
2013-06-19 1:55 ` [PATCH 2/2] user-manual: Update download size for Git and the kernel W. Trevor King
2013-06-19 17:07 ` Junio C Hamano
2013-06-22 12:40 ` W. Trevor King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vtxku112r.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=wking@tremily.us \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).