git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] Add warning when git discard changes on another branch?

From
Junio C Hamano <gitster@pobox.com>
Date
May 8, 2017, 06:07 UTC
Message-ID
<xmqq60hb9915.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170508122705.GB3540@HP>
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.

Previous: Yubin RuanNext: Yubin Ruan
Message 8 of 9 in “[RFC] Add warning when git discard changes on another branch?”
  1. Yubin RuanMay 7, 2017
  2. Junio C HamanoMay 8, 2017
  3. Yubin RuanMay 8, 2017
  4. Junio C HamanoMay 8, 2017
  5. Yubin RuanMay 8, 2017
  6. Junio C HamanoMay 8, 2017
  7. Yubin RuanMay 8, 2017
  8. Junio C HamanoMay 8, 2017
  9. Yubin RuanMay 8, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.