public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kevin F. Quinn (Gentoo)" <kevquinn@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: seeing a new trend of laziness developing.
Date: Sun, 26 Feb 2006 20:08:02 +0100	[thread overview]
Message-ID: <20060226200802.56e935ab@c1358217.kevquinn.com> (raw)
In-Reply-To: <dtss52$168$1@sea.gmane.org>

[-- 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 --]

  reply	other threads:[~2006-02-26 19:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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) [this message]
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=20060226200802.56e935ab@c1358217.kevquinn.com \
    --to=kevquinn@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