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
Adeodato Simó <dato@net.com.org.es>
Date
Jan 13, 2009, 20:10 UTC
Message-ID
<20090113201024.GA20129@chistera.yi.org>
In-Reply-To
<200901131403.16012.bss@iguanasuicide.net>
* Boyd Stephen Smith Jr. [Tue, 13 Jan 2009 14:03:11 -0600]:
> 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.

My rule for *all* of the commit message is "absolutely no more than 76 characters". With more than 76, `git log` wraps in a 80-column terminal.

Just my 2¢,
-- 
Adeodato Simó                                     dato at net.com.org.es
Debian Developer                                  adeodato at debian.org
 
La música es de los que la quieren escuchar y de nadie más.
                -- Andrés Calamaro
Previous: Boyd Stephen Smith Jr.Next: Teemu Likonen
Message 4 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.