> I'm not sure what you mean here. If you cvs commit on the webserver, the
> only bandwidth you need is for the I/O on your terminal. The CVS
> protocol traffic is only between the machine you are logged in on and
> the machine the CVS repository is on, both sf.net. And even if you
> commit directly from your own machine, CVS doesn't take a lot of
> bandwidth, very likely less than downloading the website as a tarball.

I think I should rephrase / restate what I said:

If I can do a CVS commit when I've been changing things on the webserver
from the webserver that would be good.

> Don't you have a local web server setup you can test with?
No. Besides even if I setup apache on my local machine I'd still have to
set up a database like the one used for the FAQ on sf.net 
 
> > Well I'm not really opposed to this, so what exactly would this
> > involve(getting it into CVS and then d/l'ing, updating, committing,
> > etc)? 
> 
> Creating a new module in CVS, adding the files to it and then checking
> it out on the web server.
I know what you're describing, I just don't have any idea how to do it
yet. <g>
 
> > I've thought about it a bit more and think that putting just /doc into
> > CVS may be a good idea, the other files either don't change or are
> > only changed by one person at a time / ever.
> 
> Sounds good to me, we can always add more later. So we create a module
> called website or whatever containing a doc directory? Anyone, or shall
> I?
I have no objections, btw bear in mind that I managed to delete my local
copy of dri/htdocs/ while converting to ResierFS and house cleaning so try
not to mess it up.<g>

cheers
Liam


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to