Dnia 2013-08-07, o godz. 21:02:30
Peter Stuge napisał(a):
> Tom Wijsman wrote:
> > > Besides, who does an emerge -u world without first checking to see
> > > what will be updated?
> >
> > Some people do
>
> They deserve a broken system.
Please keep your comments to yourself and do not add them
On Wed, 7 Aug 2013 21:01:06 +0200
Peter Stuge wrote:
> Tom Wijsman wrote:
> > Some people do, but that's not what this is about.
>
> They deserve a broken system.
Some people do, but that's not what this is about.
> Tom Wijsman wrote:
> > what if hell breaks loose next time?
>
> We fix it.
Fi
Tom Wijsman wrote:
> > Besides, who does an emerge -u world without first checking to see
> > what will be updated?
>
> Some people do
They deserve a broken system.
//Peter
pgp8bIGEpU77h.pgp
Description: PGP signature
Tom Wijsman wrote:
> what if hell breaks loose next time?
We fix it.
//Peter
pgpoxOD8NPi7O.pgp
Description: PGP signature
On Wed, 7 Aug 2013 09:55:05 -0400
Rich Freeman wrote:
> We're basically on the same page, so I won't respond to most of your
> email.
Same.
> I have to say that QA on Gentoo is FAR better than it ever has been in
> the past.
It is definitely very good; the only thing that currently bothers me,
On Wed, Aug 7, 2013 at 9:01 AM, Tom Wijsman wrote:
> It's at the maintainer's decision to go ahead or not; there's nobody
> going to stop the maintainer from adding it to ~. But there are people
> that going to complain (users), take action (QA), ... when hell does
> break loose because of careles
On Wed, 7 Aug 2013 08:00:51 -0400
Rich Freeman wrote:
> On Wed, Aug 7, 2013 at 6:44 AM, Tom Wijsman wrote:
> > On Sat, 3 Aug 2013 10:28:59 -0500
> > William Hubbs wrote:
> >
> >> Markos, to answer your question, there are folks on the team, and
> >> at least one user, using OpenRc from git with
On Wed, Aug 7, 2013 at 6:44 AM, Tom Wijsman wrote:
> On Sat, 3 Aug 2013 10:28:59 -0500
> William Hubbs wrote:
>
>> Markos, to answer your question, there are folks on the team, and at
>> least one user, using OpenRc from git without issues, so as far as I
>> know there shouldn't be any breakage.
On Sat, 3 Aug 2013 10:28:59 -0500
William Hubbs wrote:
> Markos, to answer your question, there are folks on the team, and at
> least one user, using OpenRc from git without issues, so as far as I
> know there shouldn't be any breakage.
A few team developers is not a large enough test base for a
William Hubbs posted on Sat, 03 Aug 2013 11:57:20 -0500 as excerpted:
> On Sat, Aug 03, 2013 at 04:44:52PM +, Duncan wrote:
>> Running the ~arch release version, OTOH, doesn't appear to
>> significantly reduce the incidence of bugs compared to live-git, but
>> there's a much bigger pile of cha
Sven Vermeulen posted on Sat, 03 Aug 2013 18:51:02 + as excerpted:
> On Sat, Aug 03, 2013 at 04:44:52PM +, Duncan wrote:
>> I run openrc- because I guess my configuration's unusual enough to
>> trigger bugs once in awhile, and from experience once I do, it's a lot
>> easier to track 'e
On Sat, Aug 3, 2013 at 11:28 AM, William Hubbs wrote:
> Ok all, I would like to appologise for the harsh wording.
Your wording wasn't harsh - it just wasn't ideal. If only imperfect
marketing was our worst problem around here...
Rich
On Sat, Aug 03, 2013 at 04:44:52PM +, Duncan wrote:
> I run openrc- because I guess my configuration's unusual enough to
> trigger bugs once in awhile, and from experience once I do, it's a lot
> easier to track 'em down if I've only a couple commits to check since my
> last update. Plu
On Sat, Aug 03, 2013 at 04:44:52PM +, Duncan wrote:
> Running the ~arch release version, OTOH, doesn't appear to significantly
> reduce the incidence of bugs compared to live-git, but there's a much
> bigger pile of changes in a release, and far less information about what
> they actually ar
William Hubbs posted on Sat, 03 Aug 2013 10:28:59 -0500 as excerpted:
> Markos, to answer your question, there are folks on the team, and at
> least one user, using OpenRc from git without issues, so as far as I
> know there shouldn't be any breakage.
The other day in the process of filing a ne
On 2013.08.03 16:28, William Hubbs wrote:
[snip]
>
> Ok all, I would like to appologise for the harsh wording.
>
> Markos, to answer your question, there are folks on the team, and at
> least one user, using OpenRc from git without issues, so as far as I
> know there shouldn't be any breakage.
>
On Sat, Aug 03, 2013 at 01:03:58PM +0300, Markos Chandras wrote:
> On Aug 3, 2013 10:06 AM, "Donnie Berkholz" wrote:
> >
> > On 15:36 Fri 02 Aug , William Hubbs wrote:
> > > All,
> > >
> > > This message is an announcement and a reminder.
> > >
> > > OpenRc-0.12 will be introduced to the porta
On 03/08/2013 13:43, Rich Freeman wrote:
[snip]
> I think the only real issue is the wording here.
[snip]
Agreed. Reading William's post, he's really just expressed in his own
words what ~arch is all about: we accept the possibility of breakage.
Everything after the first two sentences is red
On Sat, Aug 3, 2013 at 6:03 AM, Markos Chandras wrote:
> On Aug 3, 2013 10:06 AM, "Donnie Berkholz" wrote:
>> On 15:36 Fri 02 Aug , William Hubbs wrote:
>> > I do not know of any breakage personally. It does work on my system, and
>> > I know of others who are using OpenRc from git successful
On Aug 3, 2013 6:04 AM, "Markos Chandras" wrote:
>
> On Aug 3, 2013 10:06 AM, "Donnie Berkholz" wrote:
> >
> > On 15:36 Fri 02 Aug , William Hubbs wrote:
> > > All,
> > >
> > > This message is an announcement and a reminder.
> > >
> > > OpenRc-0.12 will be introduced to the portage tree in th
On Aug 3, 2013 10:06 AM, "Donnie Berkholz" wrote:
>
> On 15:36 Fri 02 Aug , William Hubbs wrote:
> > All,
> >
> > This message is an announcement and a reminder.
> >
> > OpenRc-0.12 will be introduced to the portage tree in the next few days.
> >
> > If you are using ~arch OpenRc, the standard
On 15:36 Fri 02 Aug , William Hubbs wrote:
> All,
>
> This message is an announcement and a reminder.
>
> OpenRc-0.12 will be introduced to the portage tree in the next few days.
>
> If you are using ~arch OpenRc, the standard disclaimer applies: remember
> that you might be subject to break
22 matches
Mail list logo
