From: "m h" <sesquile@gmail.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: Re: Refactoring of emerge code
Date: Tue, 9 May 2006 09:59:18 -0700 [thread overview]
Message-ID: <e36b84ee0605090959q6d7957f9v731ac83251d165ba@mail.gmail.com> (raw)
In-Reply-To: <pan.2006.05.09.09.24.52.661558@cox.net>
On 5/9/06, Duncan <1i5t5.duncan@cox.net> wrote:
> m h posted <e36b84ee0605082138t6be6ef5fk254a5f5e843b5f41@mail.gmail.com>,
> excerpted below, on Mon, 08 May 2006 21:38:49 -0700:
>
> > hat is the status of my patches? I'm assumming that they are
> > rejected... I'm curious the know the reason. If the plan is to
> > migrate to a new improved version of portage (sooner rather than
> > later), then maybe I'll try to help out Brian with his efforts.
>
> I wouldn't assume that at this point. You just provided them what, a
> couple days ago, right?
Yep, just a couple of days.
>
> On bug reports and the like, two weeks before a response isn't unusual.
> You have a couple preliminary responses here already. I'd not even
> /start/ to get antsy for two weeks, and wouldn't consider a "bump" request
> for another week after that, anyway.
I guess my concern was that there was discussion of them being tested
in IRC and I never heard any feedback from that.
My other concern is that they will get lost in the ether. (Since new
rcs seems to be coming out now).
>
> Also note that trunk is frozen. Bug fixes only until 2.1 is split off to
> stabilize. I'd not expect the patches to get in until trunk thaws again,
> for 2.2 or whatever. That means there's no immediate hurry on dealing
> with the patches, and that most of the focus ATM is on bugfixes for 2.1,
> in ordered to get the -rcs out and then the release, and get it tested and
> fully stabilized for 2006.1, now set for July, which given a 30 day
> stabilization means we need to get thru the -rcs and to release preferably
> by June first or so. I do /not/ expect your patches to get into 2.1. You
> are at least a week to 10 days too late for that.
Fair enough, if the trunk is frozen, I wish that would have been
indicated to me. No one has said that yet. The patches don't add any
functionality per se, but could be seen as bug fixes for
sloppy/extraneous code ;)
Again, this isn't supposed to be taken in the wrong way. I'm coming
from the point of view of a lurker of normal gentoo (and
user/psuedo-dev of the prefix branch (which is based on 2.1)) I
appreciate the clarification you've provided Duncan. Again, if 2.1 is
just throw-away code, then perhaps code cleanup refactoring is a waste
of effort, but I don't think it is....
-matt
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-05-09 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 6:56 [gentoo-portage-dev] Refactoring of emerge code m h
2006-04-30 0:15 ` [gentoo-portage-dev] " m h
2006-04-30 4:55 ` Alec Warner
2006-04-30 5:58 ` m h
2006-04-30 19:42 ` Alec Warner
2006-04-30 20:49 ` m h
2006-04-30 21:40 ` Donnie Berkholz
2006-05-01 20:54 ` m h
2006-05-02 7:35 ` m h
2006-05-09 4:38 ` m h
2006-05-09 9:24 ` [gentoo-portage-dev] " Duncan
2006-05-09 16:59 ` m h [this message]
2006-05-09 17:35 ` Zac Medico
2006-06-23 20:01 ` [gentoo-portage-dev] " Zac Medico
2006-06-23 20:11 ` m h
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=e36b84ee0605090959q6d7957f9v731ac83251d165ba@mail.gmail.com \
--to=sesquile@gmail.com \
--cc=gentoo-portage-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