public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] SuSE Kernel Sources
Date: Sat, 4 Oct 2003 13:14:46 +0900	[thread overview]
Message-ID: <20031004041446.GC14012%chutz@gg3.net> (raw)
In-Reply-To: <20031003105740.6e09135b.cbrewer@stealthaccess.net>

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

On 03/10/2003 at 10:57:40(-0700), C. Brewer used 1.5K just to say:
> I hear what you're saying, but I guess I wasn't particularly clear.
> Basically, you have the fix for it, and it's nice, and it works. However,
> what I was trying to get at is this- rather than write an eclass, why not
> fix the package itself and kick it back to Slack?

This idea was also in one of the comments of the bug.

http://bugs.gentoo.org/show_bug.cgi?id=23249#c13

(second comment from the bottom for now)

> Sure, there's a chance
> they won't care to change it, and the eclass would be necessary, but now
> we're at a point with everyone fixing everything, the tree is getting to
> carry almost the amount of patches as it does packages. So I apologize if
> I'm unclear or frustrated, but it feels as if rather than sharpen an old
> knife to do the work, we just make a new knife. I realize that's not the
> intent of anyone, but if the fixes and work arounds don't get back
> upstream, how long until patches and fixes do outweigh the packages?
> (I'm up to ~60k files from the ~20k when I first installed!)

-- 
/\   Georgi Georgiev   /\ A real friend isn't someone you use once and /\
\/    chutz@gg3.net    \/ then throw away. A real friend is someone    \/
/\  +81(90)6266-1163   /\ you can use over and over again.             /\

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-10-04  4:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03  1:47 [gentoo-dev] SuSE Kernel Sources Paul Varner
2003-10-03  1:58 ` Georgi Georgiev
2003-10-03  2:30   ` Paul Varner
2003-10-03  4:17     ` C. Brewer
2003-10-03  6:30       ` Georgi Georgiev
2003-10-03  7:20         ` C. Brewer
2003-10-03 13:15           ` Georgi Georgiev
2003-10-03 17:57             ` C. Brewer
2003-10-04  4:14               ` Georgi Georgiev [this message]
2003-10-03 15:10       ` Alastair Tse

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=20031004041446.GC14012%chutz@gg3.net \
    --to=chutz@gg3.net \
    --cc=chutz-dated-1066450488.902e7f53bef4@gg3.net \
    --cc=gentoo-dev@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