Re: [PATCH/RFC] Documentation: reorganize documentation of URLs understood by git

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 6, 2010, 06:57 UTC
Message-ID: <7v6345jcfq.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20100406060606.GA26629@progeny.tock>

Jonathan Nieder <jrnieder@gmail.com> writes:

> The main idea driving this for me is that the reference manual should be
> something that a sufficiently interested person could read from cover to
> cover.  As it is, there’s too much repetition for that.

I am of two minds. It is frustrating if "git clone" (or "git fetch", or "git remote") page didn't list any examples an intelligent person (or at least one who thinks he is intelligent enough) to mimic and instead referred him with "look there" indirections. While I fully share your "cover-to-cover" concern, the current organization was chosen to minimize such indirection. It is optimized for different audiences than we are (I am also from "cover-to-cover" school) who want to pick only the pages relevant to the task at hand.