From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Documenting the GRUB configure (during build)
Date: Thu, 10 Dec 2009 02:15:29 +0100 [thread overview]
Message-ID: <20091210011529.GE15546@thorin> (raw)
In-Reply-To: <4B1AD3C0.1070302@gmail.com>
On Sat, Dec 05, 2009 at 03:42:24PM -0600, Bruce Dubbs wrote:
>
> I'm afraid I don't agree that the solution to documenting changes is not
> to document anything. That may be a little harsh, but I firmly believe
> that documentation is key to acceptance.
It's OK. Well my concern is about long-term maintainability. We're very
busy all the time, and redundancy in our codebase often results in birot.
Can I count on your commitment that you'll be around to adjust this
documentation if it gets out of sync, etc?
--
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."
next prev parent reply other threads:[~2009-12-10 1:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 1:46 Documenting the GRUB configure (during build) Bruce Dubbs
2009-12-05 20:43 ` Robert Millan
2009-12-05 21:42 ` Bruce Dubbs
2009-12-06 0:03 ` Seth Goldberg
2009-12-10 1:15 ` Robert Millan [this message]
2009-12-10 21:17 ` Bruce Dubbs
2009-12-10 21:28 ` Seth Goldberg
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=20091210011529.GE15546@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.