public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Riyad Kalla" <rsk@u.arizona.edu>
To: "'Henti Smith'" <bain@tcsn.co.za>,
	"'Daniel Robbins'" <drobbins@gentoo.org>
Cc: <veldy@veldy.net>, <aurelien@gouny.org>,
	<kdolkas@telecom.ntua.gr>, <gentoo-dev@gentoo.org>,
	<manson@gentoo.org>
Subject: RE: [gentoo-dev] portage-2.0.45-r6 SERIOUSLY fucked up ?
Date: Tue, 17 Dec 2002 09:26:05 -0700	[thread overview]
Message-ID: <003601c2a5e9$032c8ed0$d628c480@rsk> (raw)
In-Reply-To: <20021217201714.0d651310.bain@tcsn.co.za>

Yes this is much better than finding a culprit, lets mass-label it.

> -----Original Message-----
> From: Henti Smith [mailto:bain@tcsn.co.za] 
> Sent: Tuesday, December 17, 2002 11:17 AM
> To: Daniel Robbins
> Cc: veldy@veldy.net; aurelien@gouny.org; 
> kdolkas@telecom.ntua.gr; gentoo-dev@gentoo.org; manson@gentoo.org
> Subject: Re: [gentoo-dev] portage-2.0.45-r6 SERIOUSLY fucked up ?
> 
> 
> On 17 Dec 2002 09:10:23 -0700
> Daniel Robbins <drobbins@gentoo.org> wrote:
> 
> > I really dislike this whole theme of finding the "culprit," since I 
> > don't think it's helpful. If you're interested, you can view the 
> > ChangeLogs here:
> 
> A typical western attitude. Something is broken/wrong find 
> somebody to blame. Addapt an eastern attidute. Something is 
> broken/wrong fix it no need to blame anybody
> 
> Henti Smith 
> 
> --
> gentoo-dev@gentoo.org mailing list
> 


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2002-12-17 16:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-17 13:18 [gentoo-dev] portage-2.0.45-r6 SERIOUSLY fucked up ? Ragnar Hojland Espinosa
2002-12-17 13:41 ` Thomas T. Veldhouse
2002-12-17 13:41 ` Jaeggi, Daniel M.
2002-12-17 13:56 ` konstantinos Dolkas
2002-12-17 13:49   ` Thomas T. Veldhouse
2002-12-17 13:53     ` Aurélien Gouny
2002-12-17 14:09       ` Thomas T. Veldhouse
2002-12-17 14:55         ` Thomas T. Veldhouse
2002-12-17 16:10           ` Daniel Robbins
2002-12-17 16:15             ` Thomas T. Veldhouse
2002-12-17 18:17             ` Henti Smith
2002-12-17 16:15               ` Adam Voigt
2002-12-17 18:35                 ` Henti Smith
2002-12-17 16:20               ` Thomas T. Veldhouse
2002-12-17 22:42                 ` Aurelien Gouny
2002-12-17 16:26               ` Riyad Kalla [this message]
2002-12-17 14:22       ` Thomas T. Veldhouse
2002-12-17 14:27         ` wes chow
2002-12-17 14:30       ` Georgios Kylafas
2002-12-17 14:38         ` [gentoo-dev] portage-2.0.45-r6 SERIOUSLY messed " Pat Double
2002-12-17 14:59           ` konstantinos Dolkas
2002-12-17 14:57             ` Pat Double
2002-12-17 15:13               ` konstantinos Dolkas
2002-12-17 15:09             ` Georgios Kylafas
     [not found]         ` <200212171612.08365.icemaze@tiscalinet.it>
2002-12-17 15:23           ` [gentoo-dev] Re: Quick and dirty system rescue (was: portage-2.0.45-r6 SERIOUSLY fucked up ?) Georgios Kylafas
  -- strict thread matches above, loose matches on Subject: below --
2002-12-17 19:40 [gentoo-dev] portage-2.0.45-r6 SERIOUSLY fucked up ? Sean P. Kane
2002-12-18  9:28 ` Ragnar Hojland Espinosa

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='003601c2a5e9$032c8ed0$d628c480@rsk' \
    --to=rsk@u.arizona.edu \
    --cc=aurelien@gouny.org \
    --cc=bain@tcsn.co.za \
    --cc=drobbins@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=kdolkas@telecom.ntua.gr \
    --cc=manson@gentoo.org \
    --cc=veldy@veldy.net \
    /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