public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] net-misc/quagga needs help
Date: Tue, 24 Jul 2012 09:21:09 +0200	[thread overview]
Message-ID: <1343114469.2180.0.camel@belkin4> (raw)
In-Reply-To: <500DCB6E.7000303@flameeyes.eu>

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

El lun, 23-07-2012 a las 15:08 -0700, Diego Elio Pettenò escribió:
> Il 23/07/2012 14:10, Peter Stuge ha scritto:
> > Did anyone report it upstream?
> 
> Not me ... because I wouldn't know which one to care about. The problem
> with upstream is that you have what they call master that is not really
> stable, then what they call 'Release Engineering' that looks like a
> kernel stable branch but they introduce new features there (instead of
> master) first.
> 
> Then there is the concept that they don't really care about doing new
> releases to fix build or run failures because they say that's what
> integrators and distributors should be paid to deal with.
> 
> I agree with you, I'd rather run bird.
> 

Will probably treeclean it in the next days if nobody is able to bump it
and make it buildable then, as looks like bird can be a good replacement

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2012-07-24  7:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 18:25 [gentoo-dev] net-misc/quagga needs help Pacho Ramos
2012-07-23 21:10 ` Peter Stuge
2012-07-23 22:08   ` Diego Elio Pettenò
2012-07-24  7:21     ` Pacho Ramos [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=1343114469.2180.0.camel@belkin4 \
    --to=pacho@gentoo.org \
    --cc=gentoo-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