From: "Mathieu Liénard--Mayor" <mathieu.lienard--mayor@ensimag.fr>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Mathieu Lienard--Mayor <Mathieu.Lienard--Mayor@ensimag.imag.fr>,
<git@vger.kernel.org>, <gitster@pobox.com>,
Jorge Juan Garcia Garcia
<Jorge-Juan.garcia-Garcia@ensimag.imag.fr>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Subject: Re: [PATCH 2/2] rm: introduce advice.rmHints to shorten messages
Date: Mon, 10 Jun 2013 09:52:25 +0200 [thread overview]
Message-ID: <19969d9996306bf0e7ac6351d4ad435d@ensibm.imag.fr> (raw)
In-Reply-To: <CALkWK0==9aN1wVoSXENvTJHOT8bd2SYrEFxrmTdhzMxB3mHPCQ@mail.gmail.com>
Le 2013-06-08 16:01, Ramkumar Ramachandra a écrit :
> Mathieu Lienard--Mayor wrote:
>> As an example, the message:
>> error: 'foo.txt' has changes staged in the index
>> (use --cached to keep the file, or -f to force removal)
>>
>> would look like, with advice.rmHints=true:
>> error: 'foo.txt' has changes staged in the index
>
> Um, have you switched the true with false? advice.* variables are
> true by default, and I turn off all of them.
Whoops, my bad, I obviously meant false.
>
> Also, I think you can extend this to also remove add-advice. Why
> would someone want to turn off advice from rm, but not add? (Unsure
> about this)
I'm not so sure i understand. Do you mean rmHints should deactivate
addHints aswell, or do you mean that since we're introducing rmHints it
would be natural to introduce addHints ?
>
>> Similarly to advice.*, advice.rmHints has been added
>> to the config variables. By default, it is set to false, in order to
>> keep the messages the same as before. When set to true, advice
>> are no longer included in the error messages.
>
> Ugh, why this roundabout-passive-past tone? Use imperative tone like
> this:
Sorry about that, we'll work on it.
>
> Introduce advice.rmHints to control the whether to display advice
> when
> using 'git rm'. Defaults to true, preserving current behavior.
--
Mathieu Liénard--Mayor,
2nd year at Grenoble INP - ENSIMAG
(+33)6 80 56 30 02
next prev parent reply other threads:[~2013-06-10 7:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 8:33 [PATCH 1/2] rm: better error message on failure for multiple files Mathieu Lienard--Mayor
2013-06-08 8:33 ` [PATCH 2/2] rm: introduce advice.rmHints to shorten messages Mathieu Lienard--Mayor
2013-06-08 14:01 ` Ramkumar Ramachandra
2013-06-10 7:52 ` Mathieu Liénard--Mayor [this message]
2013-06-10 7:55 ` Ramkumar Ramachandra
2013-06-10 8:24 ` Matthieu Moy
2013-06-10 8:26 ` Ramkumar Ramachandra
2013-06-08 13:51 ` [PATCH 1/2] rm: better error message on failure for multiple files Ramkumar Ramachandra
2013-06-10 7:43 ` Mathieu Liénard--Mayor
2013-06-10 11:28 ` Célestin Matte
-- strict thread matches above, loose matches on Subject: below --
2013-06-10 12:51 Mathieu Lienard--Mayor
2013-06-10 12:51 ` [PATCH 2/2] rm: introduce advice.rmHints to shorten messages Mathieu Lienard--Mayor
2013-06-10 12:54 ` Mathieu Liénard--Mayor
2013-06-10 16:57 ` Junio C Hamano
2013-06-10 17:17 ` Mathieu Liénard--Mayor
[not found] <1370874127-4326-1-git-send-email-Mathieu.Lienard--Mayor@ensimag.imag.fr>
2013-06-10 14:22 ` Mathieu Lienard--Mayor
2013-06-12 8:06 [PATCH v5 1/2] rm: better error message on failure for multiple files Mathieu Lienard--Mayor
2013-06-12 8:06 ` [PATCH 2/2] rm: introduce advice.rmHints to shorten messages Mathieu Lienard--Mayor
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=19969d9996306bf0e7ac6351d4ad435d@ensibm.imag.fr \
--to=mathieu.lienard--mayor@ensimag.fr \
--cc=Jorge-Juan.garcia-Garcia@ensimag.imag.fr \
--cc=Mathieu.Lienard--Mayor@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=artagnon@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.
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).