From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb@sources.redhat.com
Subject: Re: Changes to snapshot process ... ?
Date: Tue, 02 Oct 2001 08:58:00 -0000 [thread overview]
Message-ID: <3BB9E414.8090003@cygnus.com> (raw)
In-Reply-To: <2427-Tue02Oct2001101454+0300-eliz@is.elta.co.il>
>> Date: Mon, 01 Oct 2001 20:21:08 -0400
>> From: Andrew Cagney <ac131313@cygnus.com>
>>
>> I'd like to propose a change to the way sanpshots are being created. At
>> present they are being drawn strictly from the 5.1 branch. Instead, I'd
>> like to suggest running both trunk and branch snapshots. The process
>> would alternate between creating one or the other.
>
>
> Any specific reason? I rather like the way it works now.
For following both the trunk and the branch:
So that both the current branch and the current trunk get put through
the release process. That includes things like:
configury et.al. checks
ARI checks (including DOS file name checks :-)
documentation generation
as well as ending up with snaps and diffs.
Assuming I do get 5.1 (HP/UX, true64, s390) resolved I'd like to
continue making the head of 5.1 available while also publishing current
snaps.
For alternating:
That is pretty arbitrary. The objective is to constrain the volume of
raw data that shadow sites have to download every night.
An alternative would be to cut back on the snapshot frequency (weekly
only) but maintain the nightly and weekly diffs. (Although, to be
honest, that is more tricky.)
Andrew
next prev parent reply other threads:[~2001-10-02 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 17:21 Andrew Cagney
2001-10-02 1:14 ` Eli Zaretskii
2001-10-02 8:58 ` Andrew Cagney [this message]
2001-10-02 10:07 ` Eli Zaretskii
2001-10-10 21:24 ` Andrew Cagney
2001-10-11 1:06 ` Eli Zaretskii
2001-10-12 12:53 ` Andrew Cagney
2001-10-12 13:22 ` Christopher Faylor
2001-10-13 10:25 ` Andrew Cagney
2001-10-13 10:53 ` Christopher Faylor
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=3BB9E414.8090003@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox