From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
To: Christopher Faylor <cgf@redhat.com>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
overseers@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>
Subject: Re: GCC maintainer account
Date: Mon, 31 Dec 2001 19:40:00 -0000 [thread overview]
Message-ID: <orvgqah1n3.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20010216120915.C19422@redhat.com>
On Feb 16, 2001, Christopher Faylor <cgf@redhat.com> wrote:
> I don't think that group access allows modification of crontab.
This is easy to address: a crontab entry that reads a file, compares
it with the installed crontab, and updates it if they differ.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
WARNING: multiple messages have this Message-ID
From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
To: Christopher Faylor <cgf@redhat.com>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
overseers@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>
Subject: Re: GCC maintainer account
Date: Fri, 16 Feb 2001 11:24:00 -0000 [thread overview]
Message-ID: <orvgqah1n3.fsf@guarana.lsd.ic.unicamp.br> (raw)
Message-ID: <20010216112400.j7GhM5QBAkudqcRs-KXMEjYJ8Nwe2F6rR71ydYvxRzo@z> (raw)
In-Reply-To: <20010216120915.C19422@redhat.com>
On Feb 16, 2001, Christopher Faylor <cgf@redhat.com> wrote:
> I don't think that group access allows modification of crontab.
This is easy to address: a crontab entry that reads a file, compares
it with the installed crontab, and updates it if they differ.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2001-12-31 19:40 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 19:40 Mark Mitchell
2001-02-15 18:19 ` Mark Mitchell
2001-12-31 19:40 ` Andrew Cagney
2001-02-16 6:18 ` Andrew Cagney
2001-12-31 19:40 ` Christopher Faylor
2001-02-15 18:31 ` Christopher Faylor
2001-12-31 19:40 ` Mark Mitchell
2001-02-15 18:42 ` Mark Mitchell
2001-12-31 19:40 ` Chris Faylor
2001-02-15 19:10 ` Chris Faylor
2001-12-31 19:40 ` Mark Mitchell
2001-02-15 19:24 ` Mark Mitchell
2001-12-31 19:40 ` Alexandre Petit-Bianco
2001-02-15 19:33 ` Alexandre Petit-Bianco
2001-12-31 19:40 ` Chris Faylor
2001-02-15 19:41 ` Chris Faylor
2001-12-31 19:40 ` Chris Faylor
2001-02-15 19:52 ` Chris Faylor
2001-12-31 19:40 ` Mark Mitchell
2001-02-15 20:05 ` Mark Mitchell
2001-12-31 19:40 ` Mark Mitchell
2001-02-15 19:21 ` Mark Mitchell
2001-12-31 19:40 ` Jeffrey A Law
2001-02-16 7:56 ` Jeffrey A Law
2001-12-31 19:40 ` Jason Molenda
2001-02-15 20:51 ` Jason Molenda
2001-12-31 19:40 ` Mark Mitchell
2001-02-15 21:17 ` Mark Mitchell
2001-12-31 19:40 ` Christopher Faylor
2001-02-15 21:56 ` Christopher Faylor
2001-12-31 19:40 ` Gerald Pfeifer
2001-02-16 0:47 ` Gerald Pfeifer
2001-12-31 19:40 ` Christopher Faylor
2001-02-16 9:09 ` Christopher Faylor
2001-12-31 19:40 ` Phil Edwards
2001-02-16 10:17 ` Phil Edwards
2001-12-31 19:40 ` Alexandre Oliva [this message]
2001-02-16 11:24 ` Alexandre Oliva
2001-12-31 19:40 ` Mark Mitchell
2001-02-16 8:30 ` Mark Mitchell
2001-12-31 19:40 ` Andrew Cagney
2001-02-17 10:45 ` Andrew Cagney
2001-02-17 15:23 ` Phil Edwards
2001-02-17 22:25 ` Jeffrey A Law
2001-02-18 13:40 ` several messages Gerald Pfeifer
2001-12-31 19:40 ` GCC maintainer account Mark Mitchell
2001-02-17 12:10 ` Mark Mitchell
2001-02-17 17:12 ` Chris Faylor
2001-12-31 19:40 ` Andrew Cagney
2001-02-20 8:27 ` Andrew Cagney
2001-02-20 11:39 ` Andrew Cagney
2001-12-31 19:40 ` Tom Tromey
2001-02-17 15:51 ` Tom Tromey
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=orvgqah1n3.fsf@guarana.lsd.ic.unicamp.br \
--to=oliva@lsd.ic.unicamp.br \
--cc=cgf@redhat.com \
--cc=mark@codesourcery.com \
--cc=overseers@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).