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

Re: git commit --amend safety check?

From
Mike Hommey <mh@glandium.org>
Date
Mar 11, 2015, 06:33 UTC
Message-ID
<20150311063335.GA20713@glandium.org>
In-Reply-To
<CAPc5daVMec1okdBW3Wo_gEr7W3FwRwmH5pmiiMaAgGoN7MGa_A@mail.gmail.com>
On Tue, Mar 10, 2015 at 11:18:45PM -0700, Junio C Hamano wrote:
Show 9 quoted lines
> One thing we already do is to give an extra "Author: " line in the
> comment when the user edits the log message, so that it is clear
> that what is being edited is not their own work but hers. We obviously
> can add the extra warning, when the is_ancestor() thing triggers, to
> say YOU ARE REWRITING PUBLISHED HISTORY in blinking red
> bold letters there.
> 
> But the symptom indicates that they are not reading these warning
> comment.

Maybe they would if the warnings were a big paragraph *before* the commit message (but brains are easily trained to recognize patterns and skip them, so that would need to be done for very specific warnings, not for everything that's printed in a git commit editor).

Mike
Previous: Junio C HamanoNext: Jeff King
Message 5 of 8 in “git commit --amend safety check?”
  1. Shawn PearceMar 11, 2015
  2. Junio C HamanoMar 11, 2015
  3. Shawn PearceMar 11, 2015
  4. Junio C HamanoMar 11, 2015
  5. Mike HommeyMar 11, 2015
  6. Jeff KingMar 11, 2015
  7. Peter KreftingMar 11, 2015
  8. Junio C HamanoMar 11, 2015

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.