From: Paul Larson <pl@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: RE: Keep last 3 nightly builds (tarballs) around ifpossible?
Date: Tue, 05 Apr 2005 11:34:20 -0500 [thread overview]
Message-ID: <1112718860.5453.3.camel@localhost.localdomain> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3A1F@liverpoolst.ad.cl.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]
On Tue, 2005-04-05 at 01:18 +0100, Ian Pratt wrote:
> > Was wondering if it would be possible to keep around more
> > than one day's worth of unstable (and possibly testing)
> > tarballs? Perhaps 2, or even 3?
>
> Are you talking src, binaries or both?
>
> 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.
>
> 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.
--
Thanks,
Paul Larson
pl@us.ibm.com
IBM Linux Technology Center
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-04-05 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 0:18 Keep last 3 nightly builds (tarballs) around ifpossible? Ian Pratt
2005-04-05 0:24 ` Nivedita Singhvi
2005-04-05 16:34 ` Paul Larson [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-05 6:26 Fei, Fei
2005-04-05 6:55 Ian Pratt
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=1112718860.5453.3.camel@localhost.localdomain \
--to=pl@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.