David Aguilar writes:
> I was originally concerned that "git add -u" was going to die()
> and we would no longer be able to use it without pathspec.
> My concerns were unfounded.
>
> (If I am not understanding this correctly then it is a sign
> that the draft release notes can be made more clear
On Fri, Feb 22, 2013 at 9:30 AM, Junio C Hamano wrote:
> Matthieu Moy writes:
>
>> Yes, but push.default is really different: there is a config variable,
>> and we want the behavior to be configurable. In the case of "git add",
>> I don't think adding a configuration option would be the right thi
Matthieu Moy writes:
> Yes, but push.default is really different: there is a config variable,
> and we want the behavior to be configurable. In the case of "git add",
> I don't think adding a configuration option would be the right thing.
> That would mean typing "git add -u" on an account which
David Aguilar writes:
> Please enlighten me.
As you lack the knowledge of previous discussion, I think you will
be the best person to proofread the paragraph on this issue in the
"backward compatibilty notes" section of the draft release notes to
v1.8.2 to see if that is understandable to the en
David Aguilar writes:
> Please enlighten me.
> Are we really getting rid of it and replacing it with ":/"?
> That syntax looks like a meh face.. just sayin'
The current behavior is indeed replaced by "git add -u .", not ":/".
> Unlike push.default, whose warning can be silenced with configurati
On Thu, Feb 21, 2013 at 10:23 PM, Junio C Hamano wrote:
> David Aguilar writes:
>
>> When "git add -u" is invoked from a subdirectory it prints a
>> loud warning message about an upcoming Git 2.0 behavior change.
>> Some users do not care to be warned. Accomodate them.
>
> I do not think this is
David Aguilar writes:
> When "git add -u" is invoked from a subdirectory it prints a
> loud warning message about an upcoming Git 2.0 behavior change.
> Some users do not care to be warned. Accomodate them.
I do not think this is what we discussed to do.
It was very much deliberate to make the
When "git add -u" is invoked from a subdirectory it prints a
loud warning message about an upcoming Git 2.0 behavior change.
Some users do not care to be warned. Accomodate them.
The "add.silence-pathless-warnings" configuration variable can
now be used to silence this warning.
Signed-off-by: Da
8 matches
Mail list logo
