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

Re: [PATCH 3/3] Adds a #!bash to the top of bash completions so that editors can recognize, it as a bash script. Also adds a few simple comments above commands that, take arguments. The comments are meant to remind editors of potential, problems that can occur when the script is sourced on systems with "set, -u."

From
Boyd Stephen Smith Jr. <bss@iguanasuicide.net>
Date
Jan 13, 2009, 20:03 UTC
Message-ID
<200901131403.16012.bss@iguanasuicide.net>
In-Reply-To
<20090113164518.GS10179@spearce.org>
On Tuesday 2009 January 13 10:45:18 Shawn O. Pearce wrote:
>See [...] how the subject is a niceshort, one
>line summary of the module impacted and the change?

My rule for this is absolutely no more than 80 characters. Generally, you wouldn't want more than 60 or so, since it is used as the Subject: header and generally has some prefix added.

As shown says, details can go in the rest of the commit message. If you are using more than 60-80 characters even without details, you might think about splitting the patch.

>This is all based on the formatting at the time of commit.
>Anything up to the first "\n\n" in a commit message goes into the
>email subject line.

IIRC, multiple "-m" options to "git commit" will be separated by "\n\n", so that's one way to do it if you don't like your $EDITOR for some reason.

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss@iguanasuicide.net                     ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.net/                      \_/     
Previous: Shawn O. PearceNext: Adeodato Simó
Message 3 of 7 in “Adds a #!bash to the top of bash completions so that editors can recognize, it as a bash script. Also adds a few simple comments above commands that, take arguments. The comments are meant to remind editors of potential, problems that can occur when the script is sourced on systems with "set, -u."”
  1. 3/3 Adds a #!bash to the top of bash completions so that editors can recognize, it as a bash script. Also adds a few simple comments above commands that, take arguments. The comments are meant to remind editors of potential, problems that can occur when the script is sourced on systems with "set, -u."Ted Pavlic, Jan 13, 2009
  2. Shawn O. PearceJan 13, 2009
  3. Boyd Stephen Smith Jr.Jan 13, 2009
  4. Adeodato SimóJan 13, 2009
  5. Commit messagesTeemu Likonen, Jan 13, 2009
  6. Ted PavlicJan 14, 2009
  7. Markus HeidelbergJan 15, 2009

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.