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

Re: Could #-ignoring in commit message be smarter?

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Sep 4, 2010, 22:30 UTC
Message-ID
<AANLkTinTxFveiuJvCUyB5Hghj-Jy+=LfhPJhtW1UYkSH@mail.gmail.com>
In-Reply-To
<AANLkTimgt6kjTkc+gxyOmTz03bdnfiRzgt4p8vymQ=VY@mail.gmail.com>
Heya,
On Sat, Sep 4, 2010 at 17:24, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
> Where I'm referencing the #-character in the commit message itself for
> some reason, and due to word wrapping it just *happens* to end up at
> the start of a line. So the commit message silently becomes:

Isn't this rare enough that it's not really a problem? I mean, sure, when it happens it's a PITA, but it's about as painful as doing `git commit -m "Yay, it works!"` and having bash history magic blow it away. After a while you get used to it and either remember to escape the bang, or not use it?

-- 
Cheers,

Sverre Rabbelier
Previous: Ævar Arnfjörð BjarmasonNext: Ævar Arnfjörð Bjarmason
Message 2 of 3 in “Could #-ignoring in commit message be smarter?”
  1. Ævar Arnfjörð BjarmasonSep 4, 2010
  2. Sverre RabbelierSep 4, 2010
  3. Ævar Arnfjörð BjarmasonSep 4, 2010

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.