From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Ramkumar Ramachandra <artagnon@gmail•com>
Cc: "Mathieu Liénard--Mayor" <mathieu.lienard--mayor@ensimag•fr>,
"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>
Subject: Re: [PATCH 2/2] rm: introduce advice.rmHints to shorten messages
Date: Mon, 10 Jun 2013 10:24:04 +0200 [thread overview]
Message-ID: <vpqvc5mqspn.fsf@anie.imag.fr> (raw)
In-Reply-To: <CALkWK0n+yF-kRahgsQQuT-+QiT5gy=J_Bdati=uooiW0djQrgw@mail.gmail.com> (Ramkumar Ramachandra's message of "Mon, 10 Jun 2013 13:25:21 +0530")
Ramkumar Ramachandra <artagnon@gmail•com> writes:
> Mathieu Liénard--Mayor wrote:
>> 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 ?
>
> More the latter, but I'm tilting towards addRmHints (or something)
> which affects both add and rm hints.
I don't see why add and rm hints should be correlated, or I don't have
the same advice as you in mind.
$ git add foo.txt
The following paths are ignored by one of your .gitignore files:
foo.txt
Use -f if you really want to add them.
fatal: no files added
$ git rm foo.txt
error: 'foo.txt' has changes staged in the index
(use --cached to keep the file, or -f to force removal)
Both have completely different meanings: the first is about .gitignore,
and the second about not loosing data.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-06-10 8:24 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
2013-06-10 7:55 ` Ramkumar Ramachandra
2013-06-10 8:24 ` Matthieu Moy [this message]
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=vpqvc5mqspn.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=Jorge-Juan.garcia-Garcia@ensimag$(echo .)imag.fr \
--cc=Mathieu.Lienard--Mayor@ensimag$(echo .)imag.fr \
--cc=artagnon@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=mathieu.lienard--mayor@ensimag$(echo .)fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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