From: 7rans <transfire@gmail.com>
To: git@vger.kernel.org
Subject: Re: commit type
Date: Fri, 31 Oct 2008 19:20:57 +0000 (UTC) [thread overview]
Message-ID: <loom.20081031T191102-81@post.gmane.org> (raw)
In-Reply-To: ee77f5c20810311104m6044bf70r1d9d405fa04454e0@mail.gmail.com
David Symonds <dsymonds <at> gmail.com> writes:
>
> On Fri, Oct 31, 2008 at 10:58 AM, 7rans <transfire <at> gmail.com> wrote:
>
> > Currently I achieve this by adding "[type]" to the end of my commit messages.
> > But of course that's less than optimal.
>
> Why is that less than optimal? It seems a lot less intrusive than what
> you suggest.
Because it becomes formalized. Which means people can write tools other people
can use to work with them.
Having the type embedded in commit message not only clutters up the commit
messages, but different people would do it differently, using different brackets
or putting it the start or the end of the message, etc.
And of course it would be easier to ask git to list certain types of commits if
it knew about them.
7rans.
next prev parent reply other threads:[~2008-10-31 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 17:58 commit type 7rans
2008-10-31 18:04 ` David Symonds
2008-10-31 18:56 ` Samuel Lucas Vaz de Mello
2008-10-31 19:20 ` 7rans [this message]
2008-10-31 23:27 ` Johannes Schindelin
2008-11-01 4:15 ` 7rans
2008-11-02 23:02 ` bd_
2008-11-03 1:34 ` 7rans
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=loom.20081031T191102-81@post.gmane.org \
--to=transfire@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox