Introduce advice.rmHints to choose whether to display advice or not
when git rm fails. Defaults to true, in order to preserve current behavior.
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)
woul
Le 2013-06-10 18:57, Junio C Hamano a écrit :
Mathieu Liénard--Mayor writes:
Please ignore this, manipulation error while in the git send-email
command line.
Here is what my mailbox looks like (the penultimate one with 252
lines is what I am responding to).
R. [ 146: Mathieu Lienard--May
Mathieu Liénard--Mayor writes:
> Please ignore this, manipulation error while in the git send-email
> command line.
Here is what my mailbox looks like (the penultimate one with 252
lines is what I am responding to).
R. [ 146: Mathieu Lienard--Mayor ] [PATCH 1/2] rm: better error messa
R.
Introduce advice.rmHints to choose whether to display advice or not
when git rm fails. Defaults to true, in order to preserve current behavior.
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)
woul
Please ignore this, manipulation error while in the git send-email
command line.
Le 2013-06-10 14:51, Mathieu Lienard--Mayor a écrit :
Introduce advice.rmHints to choose whether to display advice or not
when git rm fails. Defaults to true, in order to preserve current
behavior.
As an example
Introduce advice.rmHints to choose whether to display advice or not
when git rm fails. Defaults to true, in order to preserve current behavior.
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)
woul
Matthieu Moy wrote:
> I don't see why add and rm hints should be correlated, or I don't have
> the same advice as you in mind.
>
> Both have completely different meanings: the first is about .gitignore,
> and the second about not loosing data.
Right, my bad. Please continue with rmHints, and opti
Ramkumar Ramachandra 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 a
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
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.t
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, hav
From: Mathieu Liénard--Mayor
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.
As an example, the message:
12 matches
Mail list logo
