bug#347: marked as done (Seth is committed new stuff to STABLE before HEAD)

[email protected] (LNX-BBC bug Tracking System)
Newsgroups gmane.linux.bbc.bugs
Message-ID <[email protected]>
Your message dated Wed, 16 Apr 2003 20:33:04 -0700
with message-id <[email protected]>
and subject line [Lnx-bbc-devel] We need to work on STABLE
has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Nick Moffitt
(administrator, LNX-BBC bugs database)

--------------------------------------
Received: (at submit) by bugs.lnx-bbc.org; 11 Apr 2003 04:29:50 +0000
From [email protected] Thu Apr 10 21:29:50 2003
Received: from goose.movealong.org ([66.93.80.69])
	by gargoyle.lnx-bbc.org with esmtp (Exim 3.35 #1 (Debian))
	id 193qAf-0004Rz-00
	for <[email protected]>; Thu, 10 Apr 2003 21:29:49 -0700
Received: by goose.movealong.org (Postfix, from userid 1001)
	id 3FCB5441F7; Thu, 10 Apr 2003 23:35:02 -0500 (CDT)
Date: Thu, 10 Apr 2003 23:35:02 -0500
From: Nate Riffe <[email protected]>
To: [email protected]
Subject: Seth is committed new stuff to STABLE before HEAD
Message-ID: <[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-pw: reindeer flotilla
User-Agent: Mutt/1.5.4i

Package: seth

STABLE is supposed to be the branch that receives code which has been
tested and shown to perform to some standard (admittedly, this
standard has not been specified yet).  However, committing changes to
STABLE first, before committing to HEAD where the testing occurs,
displays a clear disregard for this policy.

-- 
--< ((\))< >----< [email protected] >----< http://www.movealong.org/ >--
"I just feel bad for the SUVs...
  forced to live all cooped up in the city like that."
  -- The Onion, Vol.39 Issue 07
pub  1024D/05A058E0 2002-03-07 Nate Riffe (06-Mar-2002) <[email protected]>
     Key fingerprint = 0DAC F5CB D182 3165 D757  C466 CD42 12A8 05A0 58E0

---------------------------------------
Received: (at 347-done) by bugs.lnx-bbc.org; 17 Apr 2003 03:27:18 +0000
From [email protected] Wed Apr 16 20:27:18 2003
Received: from zork.zork.net ([66.92.188.166] ident=mail)
	by gargoyle.lnx-bbc.org with esmtp (Exim 3.35 #1 (Debian))
	id 19603R-0001XS-00
	for <[email protected]>; Wed, 16 Apr 2003 20:27:18 -0700
Received: from schoen by zork.zork.net with local (Exim 3.35 #1 (Debian))
	id 196092-0007nT-00; Wed, 16 Apr 2003 20:33:04 -0700
Date: Wed, 16 Apr 2003 20:33:04 -0700
From: Seth David Schoen <[email protected]>
To: [email protected]
Subject: Re: [Lnx-bbc-devel] We need to work on STABLE
Message-ID: <[email protected]>
References: <[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
X-Accept-Language: en,la,eo
X-Broadcast-Flag: 1
X-Consensus-at-Lawyerpoint: http://bpdg.blogs.eff.org/
X-Cruelty-to-Analog: http://analog.blogs.eff.org/
X-Modulation: 8/VSB Is Not A Crime
User-Agent: Mutt/1.5.3i
Sender: Seth David Schoen <[email protected]>

Nick Moffitt writes:

> Also, please check into HEAD first, and then into STABLE second.  I
> realize that Nate seems to be the only person who can build HEAD, but
> we need to make sure that HEAD doesn't lag behind STABLE.  It's okay
> if HEAD breaks, since that's not our release branch.

OK, I'll check into HEAD first, even though I can't test it.

-- 
Seth David Schoen <[email protected]> | Very frankly, I am opposed to people
     http://www.loyalty.org/~schoen/   | being programmed by others.
     http://vitanuova.loyalty.org/     |     -- Fred Rogers (1928-2003),
                                       |        464 U.S. 417, 445 (1984)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.