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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jonathan Nieder <jrnieder@xxxxxxxxx> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]