public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-core] eclass caching fix. was More unhappy news for overlay-utilizing devs :(
Date: Mon, 21 Feb 2005 22:10:34 -0600	[thread overview]
Message-ID: <20050222041033.GC29964@freedom.wit.com> (raw)
In-Reply-To: <421AAE8D.2040700@gentoo.org>

On Mon, Feb 21, 2005 at 08:01:17PM -0800, Donnie Berkholz wrote:
> If we should use it, it would be helpful if we didn't have to keep track
> of where it was (i.e., apply it to released portage as a patch).
E'yep.  :)

Until 2.0.51.16 is stabled, pushing patches into the tree isn't an option though.  Pushing out a 2.0.51-r16 isn't 
really viable.

You actually just touched on the reason why portage is jumping from .51-rN to .51.N; so we can use the -rN version 
component to push out patches while releases are being put through the testing process...
~brian

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-02-22  4:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200502181958.58079.jstubbs@gentoo.org>
     [not found] ` <200502182147.08149.jstubbs@gentoo.org>
     [not found]   ` <200502181603.53455.danarmak@gentoo.org>
     [not found]     ` <200502182309.31147.jstubbs@gentoo.org>
2005-02-22  3:02       ` [gentoo-dev] eclass caching fix. was More unhappy news for overlay-utilizing devs :( Brian Harring
2005-02-22  4:01         ` [gentoo-dev] Re: [gentoo-core] " Donnie Berkholz
2005-02-22  4:10           ` Brian Harring [this message]
2005-02-22  4:16             ` Donnie Berkholz
2005-02-22  9:43               ` Spider

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=20050222041033.GC29964@freedom.wit.com \
    --to=ferringb@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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