From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [RFC] Disabling status hints in COMMIT_EDITMSG
Date: Wed, 11 Sep 2013 09:24:16 +0200 [thread overview]
Message-ID: <vpq61u7akin.fsf@anie.imag.fr> (raw)
In-Reply-To: <xmqqeh8wzl0h.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Tue, 10 Sep 2013 09:42:06 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> But at the same time, I feel that these redundant lines, especially
> the latter one, would give the users a stronger cue than just saying
> that "bar is Untracked"; "do X to include" reminds that bar will not
> be included if nothing is done.
The one which draw my attention was "(use "git commit" to conclude
merge)" which is particularly counter-productive when you are already
doing a "git commit". The advice for untracked files is less
counter-productive, but while we're removing the non-sensical ones, I
think it makes sense to remove the essentially-useless ones too.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-09-11 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 9:19 [RFC] Disabling status hints in COMMIT_EDITMSG Matthieu Moy
2013-09-10 9:53 ` Chris Packham
2013-09-10 11:04 ` Matthieu Moy
2013-09-10 21:11 ` Chris Packham
2013-09-10 16:42 ` Junio C Hamano
2013-09-11 7:24 ` Matthieu Moy [this message]
2013-09-11 7:42 ` Javier Domingo
2013-09-11 8:05 ` Matthieu Moy
2013-09-11 9:14 ` John Szakmeister
2013-09-11 14:03 ` Javier Domingo
2013-09-11 17:24 ` Junio C Hamano
2013-09-11 17:40 ` Matthieu Moy
2013-09-10 18:03 ` 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=vpq61u7akin.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--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.
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.