From: "\"Andreas Rückert\"" <a_rueckert@gmx.net>
To: gentoo-catalyst@lists.gentoo.org
Cc: all@seniorix.com, ch@yngoor.de
Subject: Re: Re: [gentoo-catalyst] TEST REQUEST: catalyst-2.0_rc50
Date: Thu, 20 Jul 2006 21:08:53 +0200 [thread overview]
Message-ID: <20060720190853.183860@gmx.net> (raw)
In-Reply-To: <1153404657.19733.15.camel@cgianelloni.nuvox.net>
Hi!
-------- Original-Nachricht --------
Datum: Thu, 20 Jul 2006 10:10:56 -0400
Von: Chris Gianelloni <wolf31o2@gentoo.org>
An: gentoo-catalyst@lists.gentoo.org
Betreff: Re: [gentoo-catalyst] TEST REQUEST: catalyst-2.0_rc50
--<snip>--
> For "simple" builds, few changes, if any, were required. For more
> complex changes, days or even weeks of work was required to make the
> switch. To be honest, I am surprised to hear that *anyone* on this list
> is using catalyst 1.x anymore. We haven't added any code to it in over
> a year now, including any bug fixes, and have recommended to everyone to
> use catalyst 2.x instead.
Maybe it's just, that 1.x is too good to update... :-)
You know, we (as an example) are in the middle of a commercial venture, and we update, when an update is
_required_ , not when it's nice to have...
I guess you know what they say about updates. Updates means new code with new bugs, which require new
bugfixes. 1x is far from perfect, but it works for us...
Ciao,
Andreas
--
Echte DSL-Flatrate dauerhaft für 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl
--
gentoo-catalyst@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-20 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 21:56 [gentoo-catalyst] TEST REQUEST: catalyst-2.0_rc50 Chris Gianelloni
2006-07-20 7:32 ` Luca Casagrande
2006-07-20 14:10 ` Chris Gianelloni
2006-07-20 19:08 ` "Andreas Rückert" [this message]
2006-07-20 19:38 ` Andrew Gaffney
2006-07-21 8:56 ` "Andreas Rückert"
2006-07-21 16:39 ` Chris Gianelloni
2006-07-21 17:42 ` "Andreas Rückert"
2006-07-21 19:33 ` Chris Gianelloni
2006-07-20 19:50 ` Chris Gianelloni
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=20060720190853.183860@gmx.net \
--to=a_rueckert@gmx.net \
--cc=all@seniorix.com \
--cc=ch@yngoor.de \
--cc=gentoo-catalyst@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