Re: [RFC] Add warning when git discard changes on another branch?
- From
- Yubin Ruan <ablacktshirt@gmail.com>
- Date
- May 8, 2017, 14:10 UTC
- Message-ID
- <20170508141048.GA3463@HP>
- In-Reply-To
- <xmqq60hb9915.fsf@gitster.mtv.corp.google.com>
On Mon, May 08, 2017 at 03:07:02PM +0900, Junio C Hamano wrote:
Show 15 quoted lines
> Yubin Ruan <ablacktshirt@gmail.com> writes: > > > That would be helpful. But, frankly, if a user would be aware of that `advice.*' > > variable, he would have enough knowledge of Git to be aware of that situation. > > So, I think that 'M lala.txt' in transitions from branch to branch would be > > sufficient. > > Ah, you got the advice.* thing wrong. The "advice" messages are by > default noisy, and experts can turn them down by setting advice.* to > "false", saying "I know Git well enough that I do not need handholding > in this area." > > So a newbie does not have to know about "advice.*". When s/he gets > experienced enough to get annoyed by noisy messages, s/he can tune > it out.
You are right. I might have had too much drug right then... But still, I don't think that advice.* is necessary.
--- Yubin