From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Daniel Barkalow <barkalow@iabervon.org>,
Gabriel Filion <lelutin@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Subject: Re: [PATCH/RFC] Documentation: reorganize documentation of URLs understood by git
Date: Tue, 6 Apr 2010 13:10:44 +0530 [thread overview]
Message-ID: <l2hf3271551004060040v4eca088ck8f1ab3376c0f889c@mail.gmail.com> (raw)
In-Reply-To: <7v6345jcfq.fsf@alter.siamese.dyndns.org>
Hi,
> 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.
I am of the opinion that we can have both. Jonathan's document can be
a more elaborate version of the standard urls.txt included in all
these documents. I can see several usecases- for example, in documents
like remote-helpers.txt, including a full section from urls.txt would
be a bit of an overkill; we could include a reference to this document
instead. Is redundancy an issue? We'd have to update both urls.txt and
this document everytime we change something.
-- Ram
next prev parent reply other threads:[~2010-04-06 7:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 14:59 [RFC PATCH] Write new giturl(7) manpage Ramkumar Ramachandra
2010-03-29 15:48 ` Daniel Barkalow
2010-03-29 15:55 ` Ilari Liusvaara
2010-03-29 15:59 ` Sverre Rabbelier
2010-03-29 17:05 ` Ramkumar Ramachandra
2010-03-29 19:18 ` Jonathan Nieder
2010-03-29 19:21 ` Sverre Rabbelier
2010-03-29 19:24 ` Ramkumar Ramachandra
2010-03-29 19:35 ` Ramkumar Ramachandra
2010-04-06 6:06 ` [PATCH/RFC] Documentation: reorganize documentation of URLs understood by git Jonathan Nieder
2010-04-06 6:57 ` Junio C Hamano
2010-04-06 7:40 ` Ramkumar Ramachandra [this message]
2010-04-06 21:33 ` Jonathan Nieder
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=l2hf3271551004060040v4eca088ck8f1ab3376c0f889c@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ilari.liusvaara@elisanet.fi \
--cc=jrnieder@gmail.com \
--cc=lelutin@gmail.com \
--cc=srabbelier@gmail.com \
/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).