From: Junio C Hamano Date: Wed, 19 Jun 2013 21:37:47 GMT Subject: Re: [PATCH 1/2] Documentation: Update 'linux-2.6.git' -> 'linux.git' Message-ID: <7vppvhye6s.fsf@alter.siamese.dyndns.org> In-Reply-To: <20130619194709.GQ15550@odin.tremily.us> "W. Trevor King" writes: > I think any doc rewrites should be outside the scope of this patch, > which should just replace references to linux-2.6.git with linux.git > (as it does). OK. > Should the size updates from 2/2 (user-manual: Update download size > for Git and the kernel) go into the reroll, or have they been picked > up in a separate branch? I think 2/2 is fine. Here is what I'll queue. diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index e831cc2..1cbf5af 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -57,10 +57,10 @@ download a copy of an existing repository. If you don't already have a project in mind, here are some interesting examples: ------------------------------------------------ - # Git itself (approx. 10MB download): + # Git itself (approx. 40MB download): $ git clone git://git.kernel.org/pub/scm/git/git.git - # the Linux kernel (approx. 150MB download): -$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git + # the Linux kernel (approx. 640MB download): +$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ------------------------------------------------ The initial clone may be time-consuming for a large project, but you