From: Junio C Hamano <gitster@pobox.com>
To: John Tapsell <johnflux@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] Modify description file to say what this file is
Date: Tue, 17 Feb 2009 16:16:36 -0800 [thread overview]
Message-ID: <7v63j838gr.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <43d8ce650902171531r47bd79cco1524ec883e4c6114@mail.gmail.com> (John Tapsell's message of "Wed, 18 Feb 2009 08:31:08 +0900")
John Tapsell <johnflux@gmail.com> writes:
> 2009/2/18 Junio C Hamano <gitster@pobox.com>:
>
> Btw, google seems to show other programs using the description file,
> not just gitweb. How about changing it to "Unnamed repository: edit
> the file 'description' to name the repository" ?
Sure.
I also think "edit this file 'description' to name..." (not "the", but
"this") would give a bit more hint to a user with a better intuition that
the message is not something that is given by an individual program
(e.g. gitweb or the sample hook) but is a product of catting a file that
exists somewhere in the repository in question, and may reduce unnecessary
requests for help saying "The program tells me to edit 'description' file,
but where should I *create* one?"
next prev parent reply other threads:[~2009-02-18 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 10:12 [PATCH 1/2] Modify description file to say what this file is John Tapsell
2009-02-17 18:39 ` Junio C Hamano
2009-02-17 23:31 ` John Tapsell
2009-02-18 0:16 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-17 10:44 John Tapsell
2009-02-17 11:37 ` Sverre Rabbelier
2009-02-17 11:59 ` John Tapsell
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=7v63j838gr.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johnflux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.