From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Larson Subject: RE: Keep last 3 nightly builds (tarballs) around ifpossible? Date: Tue, 05 Apr 2005 11:34:20 -0500 Message-ID: <1112718860.5453.3.camel@localhost.localdomain> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0027977115==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0027977115== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-+9G9d5dKr+bQU3lD/42d" --=-+9G9d5dKr+bQU3lD/42d Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2005-04-05 at 01:18 +0100, Ian Pratt wrote: > > Was wondering if it would be possible to keep around more=20 > > than one day's worth of unstable (and possibly testing)=20 > > tarballs? Perhaps 2, or even 3? >=20 > Are you talking src, binaries or both? >=20 > I've updated the script to rename the previous night's builds to > xen-2.0-install.1.tgz the night before to .2 etc. It keeps the last > three builds. >=20 > I guess I should probably switch to using dates as snapshot identifiers, > but that requires more thought. Dates for the archived copies would be great, but if possible, it would be really nice if we could keep a consistent name for the latest snapshot. That makes automation quite a bit simpler. --=20 Thanks, Paul Larson pl@us.ibm.com IBM Linux Technology Center --=-+9G9d5dKr+bQU3lD/42d Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBCUr4LBwrpIrndMlIRAiXpAJ9EPrl2uKsbbTW8kcGvZRpef/S5TACePm0O qZrKZSS7mGFGQf4agqTmtJc= =yC3g -----END PGP SIGNATURE----- --=-+9G9d5dKr+bQU3lD/42d-- --===============0027977115== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0027977115==--