public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: law@redhat.com
To: Doug Evans <dje@sebabeach.org>
Cc: overseers@sources.redhat.com
Subject: Re: cron job
Date: Mon, 19 May 2003 16:27:00 -0000	[thread overview]
Message-ID: <200305191626.h4JGQsK2023805@speedy.slc.redhat.com> (raw)
In-Reply-To: Your message of "Fri, 16 May 2003 08:22:53 PDT." <20030516152253.492F5B53A@seba.sebabeach.org>

In message <20030516152253.492F5B53A@seba.sebabeach.org>, Doug Evans writes:
 >I'd like to set up a cron job on sources that
 >runs and creates several files for use in cgen documentation.
 >This is in addition to the cron job Ben set up to
 >generate the cgen web page.
 >
 >Any suggestions other than giving me login access?
I think we've got a special admin account for other projects to allow
this kind of thing.  That may be overkill for cgen.

I've got no objections to giving you shell access so that you can install
and maintain your cron scripts.

jeff

  reply	other threads:[~2003-05-19 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 15:21 Doug Evans
2003-05-19 16:27 ` law [this message]
2003-05-19 18:39   ` Doug Evans

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=200305191626.h4JGQsK2023805@speedy.slc.redhat.com \
    --to=law@redhat.com \
    --cc=dje@sebabeach.org \
    --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).