From: Johannes Weiner <hannes@saeurebad.de>
To: "Artem S. Tashkinov" <birdie@permonline.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GIT commit description flag(s)
Date: Sun, 16 Mar 2008 11:09:37 +0100 [thread overview]
Message-ID: <87zlsz0yla.fsf@saeurebad.de> (raw)
In-Reply-To: <47DC4104.1070109@permonline.ru> (Artem S. Tashkinov's message of "Sun, 16 Mar 2008 02:35:00 +0500")
Hi,
"Artem S. Tashkinov" <birdie@permonline.ru> writes:
> It would be nice if [kernel] git commits had a flag [a char] (or a
> combination of) describing their main purpose which could be the
> following:
>
> bug Fix [F]
> Speed up/Performance [S]
> Revert [R]
> New functionality [N]
> This way it will be much easier to keep track of important changes
> happening to the kernel.
You claim there are unimportant ones? :)
Hannes
next prev parent reply other threads:[~2008-03-16 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 21:35 GIT commit description flag(s) Artem S. Tashkinov
2008-03-16 10:09 ` Johannes Weiner [this message]
2008-03-18 16:58 ` Jan Engelhardt
2008-03-19 5:06 ` Artem S. Tashkinov
2008-03-20 11:06 ` Stefan Richter
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=87zlsz0yla.fsf@saeurebad.de \
--to=hannes@saeurebad.de \
--cc=birdie@permonline.ru \
--cc=linux-kernel@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