From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Subject: my availability
Date: Mon, 14 Sep 2009 17:50:29 +0200 [thread overview]
Message-ID: <20090914155029.GA25309@thorin> (raw)
Hi,
My vacation just finished, and I'll have less time from now on. But don't
panic ;-) I will continue to check the list and respond to issues that
require maintainer attention. I'll try to do that at least once per week
(perhaps more but I can't make a promise).
I understand the other maintainers are quite busy as well. So in order to
keep things smooth, here are two ways in which you can help:
- For obvious bug fixes, remember they can be committed straight away.
Just use common sense. Then I can oversee those changes through
commit-grub logs which is less time-consuming.
- Review other people's code and ideas. If you're reading this mail and
you think you're qualified to give your opinion, then you are. It's
much easier to approve (or disapprove) a proposed idea if others have
given their insight on it. Likewise for code.
If there's something a maintainer should urgently respond to, and has been
left unattended, feel free to contact me directly through mail or IRC.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
reply other threads:[~2009-09-14 15:50 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=20090914155029.GA25309@thorin \
--to=rmh@aybabtu.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.