From: Teemu Likonen <tlikonen@iki.fi>
To: "Adeodato Simó" <dato@net.com.org.es>
Cc: "Boyd Stephen Smith Jr." <bss@iguanasuicide.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
Ted Pavlic <ted@tedpavlic.com>, git <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Commit messages
Date: Tue, 13 Jan 2009 22:24:39 +0200 [thread overview]
Message-ID: <8763kjt0mw.fsf_-_@iki.fi> (raw)
In-Reply-To: <20090113201024.GA20129@chistera.yi.org> ("Adeodato =?iso-8859-1?Q?Sim=F3=22's?= message of "Tue\, 13 Jan 2009 21\:10\:24 +0100")
Adeodato Simó (2009-01-13 21:10 +0100) wrote:
> * Boyd Stephen Smith Jr. [Tue, 13 Jan 2009 14:03:11 -0600]:
>
>> 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.
Here's my rule:
(add-to-list 'auto-mode-alist
'("/\\.git/\\(COMMIT\\|TAG\\)_EDITMSG\\'" .
vcs-message-mode))
(define-derived-mode vcs-message-mode text-mode "VCS-message"
"Major mode for editing commit and tag messages."
(auto-fill-mode 1)
(set (make-local-variable 'tab-stop-list)
(number-sequence 4 100 4))
(setq indent-tabs-mode nil
fill-column 72
truncate-lines t))
next prev parent reply other threads:[~2009-01-13 20:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 16:11 [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." Ted Pavlic
2009-01-13 16:45 ` Shawn O. Pearce
2009-01-13 20:03 ` Boyd Stephen Smith Jr.
2009-01-13 20:10 ` Adeodato Simó
2009-01-13 20:24 ` Teemu Likonen [this message]
2009-01-14 16:55 ` Commit messages Ted Pavlic
2009-01-15 22:56 ` [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." Markus Heidelberg
2016-10-10 0:35 Commit messages Paul Eggleton
2016-10-10 3:29 ` akuster808
2016-10-10 3:46 ` Paul Eggleton
2022-03-23 6:25 [PATCH v11] drm/amdgpu: add drm buddy support to amdgpu Arunpravin Paneer Selvam
2022-03-23 6:42 ` Paul Menzel
2022-03-23 7:42 ` Christian König
2022-03-23 8:10 ` Commit messages (was: [PATCH v11] drm/amdgpu: add drm buddy support to amdgpu) Paul Menzel
2022-03-23 8:18 ` Christian König
2022-03-23 14:00 ` Daniel Stone
2022-03-23 14:42 ` Alex Deucher
2022-03-23 15:03 ` Daniel Stone
2022-03-23 15:14 ` Alex Deucher
2022-03-23 15:24 ` Daniel Stone
2022-03-23 15:32 ` [Intel-gfx] " Christian König
2022-03-25 15:56 ` Commit messages Paul Menzel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8763kjt0mw.fsf_-_@iki.fi \
--to=tlikonen@iki.fi \
--cc=bss@iguanasuicide.net \
--cc=dato@net.com.org.es \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
--cc=ted@tedpavlic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.