duplicate mails

[Brian Behlendorf <br...@collab.net>]

Looks like commits against the httpd-1.3-docs CVS tree are going to both
the apache-docs@apache.org list and new-httpd@apache.org list.  That seems
excessive.  Either it should just go to apache-docs, or a new list
apache-docs-cvs.  Comments?

	Brian

Re: duplicate mails

[Rich Bowen <rb...@rcbowen.com>]

Brian Behlendorf wrote:
> 
> Looks like commits against the httpd-1.3-docs CVS tree are going to both
> the apache-docs@apache.org list and new-httpd@apache.org list.  That seems
> excessive.  Either it should just go to apache-docs, or a new list
> apache-docs-cvs.  Comments?
> 
>         Brian

I'd prefer for them to come to apache-docs, since I watch apache-docs a
lot closer than I watch new-httpd, and I tend to miss things.

Rich
-- 
Author: Apache Server Unleashed - www.apacheunleashed.com
Director of Web Application Development - http://www.cre8tivegroup.com/

Re: duplicate mails

[Rodent of Unusual Size <Ke...@Golux.Com>]

Joshua Slive wrote:
> 
> On Tue, 31 Oct 2000, Brian Behlendorf wrote:
> >
> > Looks like commits against the httpd-1.3-docs CVS tree are
> > going to both the apache-docs@apache.org list and
> > new-httpd@apache.org list.  That seems excessive.  Either
> > it should just go to apache-docs, or a new list
> > apache-docs-cvs.  Comments?
> 
> I assume you mean they are currently going to apache-docs and
> apache-cvs?

Exactly.  That's the way it was designed, intended, and set up.
Both the developers and the docco people need to stay aware of
changes to files that affect the documentation.

If you mean something other than what Joshua mentioned above,
Brian, please let me know.  This was settled on months ago,
so I don't think it's excessive -- it's essential.
-- 
#ken    P-)}

Ken Coar                    <http://Golux.Com/coar/>
Apache Software Foundation  <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>
"Apache Server Unleashed"   <http://ApacheUnleashed.Com/>

Re: duplicate mails

[Joshua Slive <sl...@finance.commerce.ubc.ca>]

On Tue, 31 Oct 2000, Brian Behlendorf wrote:
> 
> Looks like commits against the httpd-1.3-docs CVS tree are going to both
> the apache-docs@apache.org list and new-httpd@apache.org list.  That seems
> excessive.  Either it should just go to apache-docs, or a new list
> apache-docs-cvs.  Comments?
> 

I assume you mean they are currently going to apache-docs and apache-cvs?

I don't really see a problem with the current situation.  It is good to
have the docs cvs commits going to the apache-docs list, so that everyone
here sees what is going on.  In addition, people who monitor the regular
cvs list should also be watching doc commits, since the developers are the
ones best able to tell if anything really stupid gets written in the
docs.  People reading apache-cvs are already used to the high volume, so
I doubt it bothers them.

The only thing I find irritating is getting copies of every commit that
touches a header file copied to apache-docs.  However, I don't see any way
to avoid this given that we want people in apache-docs to have access to
the API docs.

Joshua.