public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zachary Grafton <zachary.grafton@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Again: Critical bugs considered invalid
Date: Sat, 9 Jun 2007 02:49:50 -0400	[thread overview]
Message-ID: <200706090249.50881.zachary.grafton@gmail.com> (raw)
In-Reply-To: <200706090129.37942.volker.armin.hemmann@tu-clausthal.de>

On Friday 08 June 2007 19:29, Hemmann, Volker Armin wrote:
> On Samstag, 9. Juni 2007, »Q« wrote:
> > In <news:200706081440.37381.volker.armin.hemmann@tu-clausthal.de>,
> >
> > "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de> wrote:
> > > On Freitag, 8. Juni 2007, Alexander Skwar wrote:
> > > > b.n. <brullonulla@gmail.com> wrote:
> > > > > Really. If you think there's a problem, explain it. You get
> > > > > attacked? Insist. Prove them they are wrong.
> > > >
> > > > Just curious: Did you ever try this with Jakub?
> > >
> > > I did.
> > >
> > > And after some arguments a different dev came in and recognized the
> > > bug as a real bug...
> >
> > I've seen that happen a few times.  IME, jakub is usually right, but
> > whether he's right or wrong he's very stubborn.  It's possible to
> > wrangle the bug yourself, asking another dev to have a look at it,
> > instead of arguing with Jakub until somebody notices.
>
> Jakub is like a spam filter who filters out 100% of the spam. Sadly, he
> filters a fair amount of ham too - and if your ham got filtered the option
> to get it recognized as ham are hard to find and not easy to use ;)
>
> His user interface could be improved....

Maybe someone should submit a bug report....
--
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-06-09  6:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 23:34 [gentoo-user] Again: Critical bugs considered invalid Davi
2007-06-07  0:01 ` Enrico Weigelt
2007-06-07 23:21   ` b.n.
2007-06-08  7:57     ` [gentoo-user] " Alexander Skwar
2007-06-08 10:39       ` b.n.
2007-06-08 12:40       ` Hemmann, Volker Armin
2007-06-08 22:29         ` »Q«
2007-06-08 23:29           ` Hemmann, Volker Armin
2007-06-09  6:49             ` Zachary Grafton [this message]
2007-06-09  9:05               ` Kent Fredric
2007-06-09  9:46                 ` Dale
2007-06-09 10:19                   ` Kent Fredric
2007-06-09 13:11                     ` Dale
2007-06-09 13:24                       ` Dale
2007-06-09 17:42                       ` Bo Ørsted Andresen
2007-06-10  1:30                         ` Dale
2007-06-08 14:04     ` [gentoo-user] " Enrico Weigelt
2007-06-08 23:25       ` b.n.
2007-06-12 17:08         ` Enrico Weigelt
2007-06-12 19:25           ` Kent Fredric
  -- strict thread matches above, loose matches on Subject: below --
2007-06-05 15:07 Enrico Weigelt
2007-06-05 15:45 ` Hemmann, Volker Armin
2007-06-06 21:51   ` Enrico Weigelt
2007-06-06 22:01     ` Hemmann, Volker Armin
2007-06-06 23:10       ` Enrico Weigelt
2007-06-07  7:11         ` [gentoo-user] " Alexander Skwar
2007-06-07  7:10     ` Alexander Skwar
2007-06-05 15:48 ` [gentoo-user] " Hans-Werner Hilse
2007-06-06 22:03   ` Enrico Weigelt
2007-06-07  2:58     ` [gentoo-user] " »Q«
2007-06-06  7:14 ` Alexander Skwar

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=200706090249.50881.zachary.grafton@gmail.com \
    --to=zachary.grafton@gmail.com \
    --cc=gentoo-user@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