From: Collins Richey <crichey@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] proposed patch
Date: Tue, 22 Feb 2005 07:09:16 -0700 [thread overview]
Message-ID: <e00942e405022206096167aa4b@mail.gmail.com> (raw)
In-Reply-To: <20050222115506.GA13882@phaenix.haell.com>
On Tue, 22 Feb 2005 03:55:06 -0800, Drake Wyrm <wyrm@haell.com> wrote:
> This is actually an excellent illustration of my point. The patch I
> mentioned as an example changes almost nothing. It adds one file and
> touches the makefiles so that the build process notices it. Its
> inclusion would be completely benign.
>
Sit back in your chair and think about that at least twice! I've been
working in the computer industry for 30+ years, and I can't even begin
to count the times when a total outage was followed by the excuse "But
I just changed one line!".
--
Collins
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2005-02-22 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <36acd65c050220230928e76206@mail.gmail.com>
2005-02-21 10:34 ` [gentoo-dev] proposed patch Aaron Walker
2005-02-21 17:58 ` Greg KH
2005-02-22 3:01 ` Drake Wyrm
2005-02-22 7:40 ` Greg KH
2005-02-22 11:55 ` Drake Wyrm
2005-02-22 14:09 ` Collins Richey [this message]
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=e00942e405022206096167aa4b@mail.gmail.com \
--to=crichey@gmail.com \
--cc=gentoo-dev@lists.gentoo.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