public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <bugs@dev.gentooexperimental.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: OT: offensive (Re: [gentoo-dev] explicit -r0 in ebuild filename)
Date: Mon, 31 Mar 2008 10:29:33 +0200	[thread overview]
Message-ID: <47F0A0ED.40405@dev.gentooexperimental.org> (raw)
In-Reply-To: <97a4d67e0803310049j34de0ae1jc7ecff5563141d7e@mail.gmail.com>

Anders Ossowicki wrote:
> On 31/03/2008, *Thilo Bangert* <bangert@gentoo.org 
> <mailto:bangert@gentoo.org>> wrote:
>
>     > Please think things through before asking to have pkgcore's bugs
>     > 'fixed' via specification next time...
>
>     maybe my english language skills or social interaction qualities are
>     failing me, but i find the above sentence highly offensive.
>
>
> pkgcore crashes on ebuilds with explicit -r0 in the PV, which led to 
> Brian Harring bringing this entire discussion up in the first place. 
> Rather than getting pkgcore to handle -r0 correctly, he decided to try 
> and get it banned through the specification.
That bug has been adressed, still leaves the underlying problem wether 
to allow this ambiguity or not. If you have the patience to read the 
pingpong between Harring and McCreesh the current discussion is wether 
that format even makes sense, not wether a fixed bug in a third-party 
app is relevant.
>
> Please note, the above does not imply anything about my feelings 
> towards the original proposal, so please don't take it as such. I 
> really couldn't care less what you decide to do or not do.
>
>     am i too thin skinned for gentoo-dev?
>
> In this particular case, I'd say yes :-)
I'd say no. There's no need for ad hominem attack in what is supposed to 
be a technical discussion.
-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-31  8:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-30  2:39 [gentoo-dev] explicit -r0 in ebuild filename Brian Harring
2008-03-30  2:48 ` Ciaran McCreesh
2008-03-30  3:12   ` Brian Harring
2008-03-30  3:20     ` Ciaran McCreesh
2008-03-30  4:16       ` Brian Harring
2008-03-30  4:40         ` Ciaran McCreesh
2008-03-30  9:39           ` Brian Harring
2008-03-30 13:10             ` [gentoo-dev] " Duncan
2008-03-30 14:54               ` Marijn Schouten (hkBst)
2008-03-30 15:38                 ` Ioannis Aslanidis
2008-03-30 17:56                   ` Richard Freeman
2008-03-30 18:26             ` [gentoo-dev] " Ciaran McCreesh
2008-03-30 16:24   ` Mike Frysinger
2008-03-30 18:18     ` Ciaran McCreesh
2008-03-30 18:59       ` Mike Frysinger
2008-03-30 23:40         ` Brian Harring
2008-03-30 23:46           ` Ciaran McCreesh
2008-03-31  0:02             ` Brian Harring
2008-03-31  0:06               ` Ciaran McCreesh
2008-03-31  0:29                 ` Brian Harring
2008-04-01 10:44                   ` Ciaran McCreesh
2008-04-04  6:39                   ` Bo Ørsted Andresen
2008-03-31  7:40   ` OT: offensive (Re: [gentoo-dev] explicit -r0 in ebuild filename) Thilo Bangert
2008-03-31  7:49     ` Anders Ossowicki
2008-03-31  8:29       ` Patrick Lauer [this message]
2008-03-31  8:48         ` Anders Ossowicki
2008-03-31 16:07     ` Jeroen Roovers
2008-03-30  3:36 ` [gentoo-dev] Re: explicit -r0 in ebuild filename Michael Sterrett -Mr. Bones.-
2008-03-30  3:41   ` Ciaran McCreesh

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=47F0A0ED.40405@dev.gentooexperimental.org \
    --to=bugs@dev.gentooexperimental.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