From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Jasmine <jasmine.chua@securecirt.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] nagios ebuilds.
Date: 16 Sep 2003 09:05:30 -0400 [thread overview]
Message-ID: <1063717529.2742.15.camel@localhost> (raw)
In-Reply-To: <200309160627.14093.jasmine.chua@securecirt.com>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
On Mon, 2003-09-15 at 18:27, Jasmine wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> > One way would be to post the fixed ebuilds into a bug (or into the bugs
> > they solve). Unfortunately, without the help of a developer with CVS
> > access, you can't do much other than that.
>
> Hi
>
> Hmm.. I am a gentoo developer for nagios if you take a look at the 4th August
> GWN :-)
> Don't all developers get CVS access?
Yes, once you have completed your trial period and passed the quiz, you
should have access added, along with your @gentoo.org email address. If
you are still in your trial period, then all your commits to CVS must be
made through another developer (preferably your mentor) until your trial
period is over.
If you should have access to CVS and do not, then you should contact
klieber or seemant and get your access added.
--
Chris Gianelloni
Developer, Gentoo Linux
Games Team
Is your power animal a pengiun?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-16 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 19:56 [gentoo-dev] nagios ebuilds Jasmine
2003-09-15 21:06 ` Chris Gianelloni
2003-09-15 22:27 ` Jasmine
2003-09-15 22:54 ` Brian Jackson
2003-09-16 13:05 ` Chris Gianelloni [this message]
2003-09-19 11:43 ` Jasmine
2003-09-19 12:58 ` Chris Gianelloni
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=1063717529.2742.15.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=jasmine.chua@securecirt.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