From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] seeing a new trend of laziness developing.
Date: Sun, 26 Feb 2006 11:40:44 -0500 [thread overview]
Message-ID: <1140972044.2937.29.camel@localhost> (raw)
When people go out of their way to file a bug for you or a team you are
on. Please _please_ don't be lazy and just close/reassign/other it
with a '.'
A period is the most useless way to respond to a bug. If you can't take
2 seconds out of your life to say something as simple as. 'Fixed in
CVS/This is an upstream problem/etc' or anything slightly descriptive of
what changed. Then your use usefulness to the project starts to come in
question.
Continuing to close bugs with a simple '.' will result in me making fun
of you rightly every time I see your name mentioned anywhere.
232 matches. http://tinyurl.com/pmrmx
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2006-02-26 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 16:40 Ned Ludd [this message]
2006-02-26 17:12 ` [gentoo-dev] seeing a new trend of laziness developing Tim Yamin
2006-02-26 18:30 ` [gentoo-dev] " R Hill
2006-02-26 19:08 ` Kevin F. Quinn (Gentoo)
2006-02-27 3:18 ` R Hill
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=1140972044.2937.29.camel@localhost \
--to=solar@gentoo.org \
--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