From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 7 Mar 2008 06:51:35 +0300 From: Alexey Tourbin To: devel@lists.altlinux.org Message-ID: <20080307035135.GJ7797@solemn.turbinal> Mail-Followup-To: devel@lists.altlinux.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ofZMSlrAVk9bLeVm" Content-Disposition: inline Subject: [devel] Fwd: Re: Getting "SO Yesterday" blead via git X-BeenThere: devel@lists.altlinux.org X-Mailman-Version: 2.1.10b3 Precedence: list Reply-To: ALT Linux Team development discussions List-Id: ALT Linux Team development discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2008 03:56:05 -0000 Archived-At: List-Archive: List-Post: --ofZMSlrAVk9bLeVm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable ----- Forwarded message from Nicholas Clark ----- Date: Thu, 6 Mar 2008 14:12:56 +0000 From: Nicholas Clark Subject: Re: Getting "SO Yesterday" blead via git To: Rafael Garcia-Suarez Cc: Sam Vilain , Perl 5 Porters Message-ID: <20080306141256.GB79799@plum.flirble.org> User-Agent: Mutt/1.4.2.1i On Thu, Mar 06, 2008 at 03:04:06PM +0100, Rafael Garcia-Suarez wrote: > Currently we cherry-pick from blead into maint-*. This is a bit > inconvenient, since we need to track what commits have been reviewed or > not. I was thinking about making a maint-5.10-review branch that follows > blead by fast-forward, and that says "up to this point we have reviewed > patches and the relevant ones have been cherry-picked into maint-5.10". > How sane does this sound? A simple fast-forward on one branch doesn't actually work. There a lot of patches that I find I want to cherry pick, but they are wait= ing on some other fix. Meanwhile other patches are committed to trunk. I don't think that a "don't do that" is going to work, because Perl is sufficiently big and sufficiently diverse that we're not going to find out that some blead patches are actually troublesome until some days (or even weeks) after they are committed, because of the diverse nature of platforms and configurations upon which Perl builds and is built. Patches really need a third state of "maybe", with annotations on why it's maybe. Nicholas Clark ----- End forwarded message ----- --ofZMSlrAVk9bLeVm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (GNU/Linux) iEYEARECAAYFAkfQu8cACgkQfBKgtDjnu0bYagCfYlzxB34EKf6ihdSBB8BZP14i AZUAoOkHyE7lE4DHxhYdYj7vZc7qgqLL =ApD/ -----END PGP SIGNATURE----- --ofZMSlrAVk9bLeVm--