From: Christopher Faylor <cgf@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: "Joseph S. Myers" <jsm28@cam.ac.uk>, overseers@sources.redhat.com
Subject: Re: sources.redhat.com downtime
Date: Fri, 17 Jan 2003 16:20:00 -0000 [thread overview]
Message-ID: <20030117162142.GI4335@redhat.com> (raw)
In-Reply-To: <3E282B74.30805@redhat.com>
On Fri, Jan 17, 2003 at 11:12:36AM -0500, Andrew Cagney wrote:
>>On Fri, Jan 17, 2003 at 11:19:06AM +0000, Joseph S. Myers wrote:
>>
>>>On Thu, 16 Jan 2003, Andrew Cagney wrote:
>>>
>>
>>>>> I can set the time to GMT on the new system, if everybody agrees that
>>>>is
>>>>> reasonable. It seems reasonable to me.
>>
>>>>
>>>>Yes please. This was discussed before, the consensus then being that a
>>>>new machine could have this change (just not the old machine).
>>
>>>
>>>Thanks, just note if fixing up crontabs that at least gccadmin's crontab
>>>is CVS-controlled (/cvs/gcc/gcc/maintainer-scripts/) - I don't know about
>>>others, but presume in general that jobs should continue to run at the
>>>same absolute time each day.
>>
>>
>>Is there any reason why I can't leave that to the maintainers of the
>>individual
>>crontab owners? I do have all of the crontab entries running, but getting
>>the
>>times right could be tricky. You can't just add 8 to the hours, obviously.
>
>None.
>
>In fact I think gcc and gdb's cron should start out disabled. Relevent
>admins can re-start them with adjusted timezones once other things have
>settled.
That is actually what I've done. The crontab entries are there but they
are commented out.
cgf
(already stressed with a day to go)
next prev parent reply other threads:[~2003-01-17 16:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 21:08 Christopher Faylor
2003-01-16 21:21 ` Andrew Cagney
2003-01-16 22:07 ` Christopher Faylor
2003-01-16 22:04 ` Benjamin Kosnik
2003-01-16 22:24 ` Jonathan Larmour
2003-01-16 22:39 ` Confirmed: " Christopher Faylor
2003-01-16 22:57 ` Andrew Cagney
2003-01-16 23:07 ` Christopher Faylor
2003-01-16 22:40 ` Joseph S. Myers
2003-01-16 23:08 ` Christopher Faylor
2003-01-16 23:13 ` Andrew Cagney
2003-01-16 23:27 ` Jason Molenda
2003-01-17 11:19 ` Joseph S. Myers
2003-01-17 15:36 ` Christopher Faylor
2003-01-17 15:59 ` Alexandre Oliva
2003-01-17 16:08 ` Christopher Faylor
2003-01-17 16:12 ` Andrew Cagney
2003-01-17 16:20 ` Christopher Faylor [this message]
2003-01-17 19:37 ` Hans-Peter Nilsson
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=20030117162142.GI4335@redhat.com \
--to=cgf@redhat.com \
--cc=ac131313@redhat.com \
--cc=jsm28@cam.ac.uk \
--cc=overseers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).