* [gentoo-dev] seeing a new trend of laziness developing.
@ 2006-02-26 16:40 Ned Ludd
2006-02-26 17:12 ` Tim Yamin
2006-02-26 18:30 ` [gentoo-dev] " R Hill
0 siblings, 2 replies; 5+ messages in thread
From: Ned Ludd @ 2006-02-26 16:40 UTC (permalink / raw
To: gentoo-dev
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-dev] seeing a new trend of laziness developing.
2006-02-26 16:40 [gentoo-dev] seeing a new trend of laziness developing Ned Ludd
@ 2006-02-26 17:12 ` Tim Yamin
2006-02-26 18:30 ` [gentoo-dev] " R Hill
1 sibling, 0 replies; 5+ messages in thread
From: Tim Yamin @ 2006-02-26 17:12 UTC (permalink / raw
To: gentoo-dev
On Sun, Feb 26, 2006 at 11:40:44AM -0500, Ned Ludd wrote:
> 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
Needless to say, the same applies for CVS. *Always* commit with a ChangeLog
entry and never use "See ChangeLog" as your CVS commit message -- this
makes tracking down changes very difficult due to the non-atomic nature
of CVS.
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-dev] Re: seeing a new trend of laziness developing.
2006-02-26 16:40 [gentoo-dev] seeing a new trend of laziness developing Ned Ludd
2006-02-26 17:12 ` Tim Yamin
@ 2006-02-26 18:30 ` R Hill
2006-02-26 19:08 ` Kevin F. Quinn (Gentoo)
1 sibling, 1 reply; 5+ messages in thread
From: R Hill @ 2006-02-26 18:30 UTC (permalink / raw
To: gentoo-dev
Ned Ludd wrote:
> 232 matches. http://tinyurl.com/pmrmx
The vast majority of which have an explanation in the comment directly preceding.
--de.
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-dev] Re: seeing a new trend of laziness developing.
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
0 siblings, 1 reply; 5+ messages in thread
From: Kevin F. Quinn (Gentoo) @ 2006-02-26 19:08 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
On Sun, 26 Feb 2006 12:30:50 -0600
R Hill <dirtyepic.sk@gmail.com> wrote:
> Ned Ludd wrote:
>
> > 232 matches. http://tinyurl.com/pmrmx
>
> The vast majority of which have an explanation in the comment
> directly preceding.
In which case it's a moment's effort to cut-n-paste the text into the
reassignment/resolution comment. Hence solar's laziness accusation.
I'd go further, and suggest that sometimes it's not just laziness (since
cut-n-paste isn't any more effort than typing '.') but a deliberate
action to avoid explaining oneself.
When re-assigning, it is extremely useful for the new assignee to see
some relevant text, as this is the first bit of text they may see. If
you just re-assign with '.' then the new assignee has to browse the bug
to decide how to prioritise etc - which means flipping from your email
client to the web browser or whatever. All of this breaks up
processing the stream of stuff coming from bugzilla, causing wasted
time - all because someone was deliberately evasive about why they
reassigned.
Similarly when resolving, just saying '.' means other interested parties
have to browse the bug to check whether the resolution is valid or not
- if there's a decent comment along with the resolution this becomes
unnecessary in the majority of cases.
--
Kevin F. Quinn
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-dev] Re: seeing a new trend of laziness developing.
2006-02-26 19:08 ` Kevin F. Quinn (Gentoo)
@ 2006-02-27 3:18 ` R Hill
0 siblings, 0 replies; 5+ messages in thread
From: R Hill @ 2006-02-27 3:18 UTC (permalink / raw
To: gentoo-dev
Kevin F. Quinn (Gentoo) wrote:
> When re-assigning, it is extremely useful for the new assignee to see
> some relevant text, as this is the first bit of text they may see. If
> you just re-assign with '.' then the new assignee has to browse the bug
> to decide how to prioritise etc - which means flipping from your email
> client to the web browser or whatever. All of this breaks up
> processing the stream of stuff coming from bugzilla, causing wasted
> time - all because someone was deliberately evasive about why they
> reassigned.
Right, sorry. I wasn't thinking in the context of bugmail.
--de.
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-02-27 3:23 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-26 16:40 [gentoo-dev] seeing a new trend of laziness developing Ned Ludd
2006-02-26 17:12 ` 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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox