From: Jon Portnoy <avenj@gentoo.org>
To: Matt Tucker <tuck@whistlingfish.net>
Cc: Spider <spider@gentoo.org>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage Integrity (Was: gcc ebuild's, downgrades, deletion etc)
Date: Fri, 14 Mar 2003 18:23:44 -0500 [thread overview]
Message-ID: <20030314232344.GA29578@cerberus.oppresses.us> (raw)
In-Reply-To: <20030314231709.GA29451@cerberus.oppresses.us>
On Fri, Mar 14, 2003 at 06:17:09PM -0500, Jon Portnoy wrote:
> On Fri, Mar 14, 2003 at 03:12:04PM -0800, Matt Tucker wrote:
> > -- Spider <spider@gentoo.org> spake thusly:
> >
> > > begin quote
> > > On Fri, 14 Mar 2003 06:19:17 -0700
> > > Alain Penders <alain@gentoo.org> wrote:
[snip]
>
> My opinion here is: if you don't have the time to take a look at the
> diff, don't accept the bug containing the ebuild. Pass it on to someone
> who does have the time rather than risk borkage by just copying the old
> ebuild.
>
Just to add a few more thoughts: the user took the time to modify the
old ebuild to work properly with the new version, test it, and submit it
- a significant investment of time. To then not even take the time to do
a diff and look over the changes is the same as saying "I don't value
your contribution." That's not a good approach at all and certainly
won't encourage people to help out.
--
Jon Portnoy
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-03-14 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 8:43 [gentoo-dev] gcc ebuild's, downgrades, deletion etc Phil Richards
2003-03-14 0:47 ` [gentoo-dev] Portage Integrity (Was: gcc ebuild's, downgrades, deletion etc) Todd Wright
2003-03-14 12:27 ` Spider
2003-03-14 13:19 ` Alain Penders
2003-03-14 13:32 ` Spider
2003-03-14 23:12 ` Matt Tucker
2003-03-14 23:17 ` Jon Portnoy
2003-03-14 23:23 ` Jon Portnoy [this message]
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=20030314232344.GA29578@cerberus.oppresses.us \
--to=avenj@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=spider@gentoo.org \
--cc=tuck@whistlingfish.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