public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Food for thought (CVS access)
Date: 08 Feb 2002 18:10:39 -0700	[thread overview]
Message-ID: <1013217039.2815.210.camel@inventor.gentoo.org> (raw)
In-Reply-To: <1013204275.15050.36.camel@silica.localmosci>

On Fri, 2002-02-08 at 14:37, Tod M. Neidt wrote:
> Hi!
> 
> Just gave the "How to Become a FreeBSD Committer" article over at
> O'Reilly a read.
> http://www.onlamp.com/pub/a/bsd/2002/01/31/Big_Scary_Daemons.html
> 
> Thought that it might be of general interest to this list because there
> have been inquiries recently concerning Gentoo CVS access.
> 
> DISCLAIMER: This link is provided for informational purposes only. It
> does *not* necessarily reflect the views of the Management, i.e.
> drobbins.  

Thanks for the post... it's interesting how our development process is
gradually becoming more and more like the way the FreeBSD guys are doing
things.  Definitely some good ideas in the article and in the FreeBSD
Comitter's Guide link in the article.  Another situation where we need
to start defining some clear but not overly-burdensome policy! :)

Thanks for the post.

Best Regards,

-- 
Daniel Robbins                                  <drobbins@gentoo.org>
Chief Architect/President                       http://www.gentoo.org 
Gentoo Technologies, Inc.



      reply	other threads:[~2002-02-09  1:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08 21:37 [gentoo-dev] Food for thought (CVS access) Tod M. Neidt
2002-02-09  1:10 ` Daniel Robbins [this message]

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=1013217039.2815.210.camel@inventor.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /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