public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <webmaster@hartwork.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] `paludis --info' is not like `emerge --info'
Date: Mon, 13 Apr 2009 23:50:07 +0200	[thread overview]
Message-ID: <49E3B38F.1020003@hartwork.org> (raw)
In-Reply-To: <20090413132938.14c426e5@snowcone>

Ciaran McCreesh wrote:
> Taking any of it out would be
> removing things that are required to determine the cause of a bug.

I doubt that's true in most cases:  The information needed to
finding the bug is a (possibly small) subset of the whole.

I don't see how additionally providing a stripped down version of
paludis info hurts anybody, as the subset either holds what the
wrangler needs or it doesn't, in which case they can still request
more information for the reporter.

I suggest that you take this as a usability request from the users
of your software.  Isn't that a great chance to make several people
happier every day in the future by just a few lines of code on your end?
Would they raise their voice if it did not matter?



Sebastian



  reply	other threads:[~2009-04-13 21:50 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 22:22 [gentoo-dev] `paludis --info' is not like `emerge --info' Jeroen Roovers
2009-02-18 22:35 ` Dawid Węgliński
2009-02-18 22:38   ` Jeroen Roovers
2009-02-18 22:55 ` Ciaran McCreesh
2009-02-18 23:03   ` Jeroen Roovers
2009-02-18 23:24     ` Ciaran McCreesh
2009-02-18 23:39       ` Stelian Ionescu
2009-02-18 23:42         ` Ciaran McCreesh
2009-02-18 23:48       ` Jeroen Roovers
2009-02-18 23:08   ` Jeroen Roovers
2009-04-04 13:17   ` Peter Alfredsen
2009-04-04 13:47     ` Ciaran McCreesh
2009-04-04 16:12       ` Thilo Bangert
2009-04-04 16:36         ` Matti Bickel
2009-04-05 20:41         ` Timothy Redaelli
2009-04-06  3:29           ` Andrew D Kirch
2009-04-06  3:35             ` Andrew Gaffney
2009-04-06  3:49               ` Andrew D Kirch
2009-04-06  3:55                 ` Nirbheek Chauhan
2009-04-06  4:42                   ` Andrew D Kirch
2009-04-06 16:25                     ` Richard Freeman
2009-04-06  9:32             ` Timothy Redaelli
2009-04-06 10:16               ` [gentoo-dev] " Duncan
2009-04-06  8:11           ` [gentoo-dev] " Peter Volkov
2009-04-08 14:36             ` Jeroen Roovers
2009-04-28 20:15               ` Peter Volkov
2009-04-08 19:13             ` Zac Medico
2009-04-13 12:21     ` Sebastian Pipping
2009-04-13 12:29       ` Ciaran McCreesh
2009-04-13 21:50         ` Sebastian Pipping [this message]
2009-04-13 21:55           ` Ciaran McCreesh
2009-04-14  0:29             ` Richard Freeman
2009-04-14  1:32               ` [gentoo-dev] " Duncan
2009-05-09 21:14 ` [gentoo-dev] " Thomas Anderson
2009-05-10  3:23   ` Nirbheek Chauhan
2009-05-10  9:21     ` David Leverton

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=49E3B38F.1020003@hartwork.org \
    --to=webmaster@hartwork.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