From: Christoph Michelbach <michelbach94@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Documentation of post-receive hook
Date: Wed, 22 Nov 2017 20:09:20 +0100 [thread overview]
Message-ID: <1511377760.11458.0.camel@gmail.com> (raw)
In-Reply-To: <xmqqlgizyv0o.fsf@gitster.mtv.corp.google.com>
On Wed, 2017-11-22 at 10:14 +0900, Junio C Hamano wrote:
> Your suggesting to mention that particular message hints at me that
> you feel that the users may not necessarily understand that push did
> not result in any update of references on the other side when they
> see it. If the message was clear enough to them, "when it reacts to
> push and updates" ought to be clear enough description, too.
>
> And if that indeed is the case (and I would not be surprised if it
> is, but I suspect that most users are clueful enough), it is not the
> documentation, but the "Already up-to-date" message, that needs to
> be clarified, no?
>
> Besides, we'd rather not cast the end-user facing message in stone
> in the documentation like that (especially when the message has
> known room for improvement and will change).
You're right (with everything you wrote). Your proposed text sounds good.
next prev parent reply other threads:[~2017-11-22 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 22:40 Documentation of post-receive hook Christoph Michelbach
2017-11-17 1:41 ` Junio C Hamano
2017-11-17 3:24 ` Junio C Hamano
2017-11-19 17:31 ` Christoph Michelbach
2017-11-19 17:42 ` Robert P. J. Day
2017-11-19 18:55 ` Christoph Michelbach
2017-11-20 1:17 ` Junio C Hamano
2017-11-21 23:44 ` Christoph Michelbach
2017-11-22 1:14 ` Junio C Hamano
2017-11-22 19:09 ` Christoph Michelbach [this message]
2017-11-24 2:10 ` Re*: " Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1511377760.11458.0.camel@gmail.com \
--to=michelbach94@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).