From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Changelog rules relaxation. My activity
Date: Wed, 16 Jan 2013 13:18:43 +0100 [thread overview]
Message-ID: <50F69AA3.8050100@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
Hello, all. I'll be intensively going through mail/bugs this weekend and
subsequent time. There is quite a lot of it. If your issue isn't
addressed by February, please send a reminder. Also a reminder for your
unanswered thread before this weekend is appreciated so I know which
threads are still active.
Also due to advance in VCS our current Changelog verbosity is way too
much and is something from another century. You still have to put a log
entry in Changelog for every commit but no need to mention all files
unless you need to add some notice (then it may be better to be a
comment in appropriate place) or if this mention is
copyright-significant (e.g. import from other project) in which case it
needs to be approved by a maintainer, mentioned in the appropriate
space, and, if technically reasonable, put it into a separate directory
under grub-core/lib.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
reply other threads:[~2013-01-16 12:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50F69AA3.8050100@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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 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.