Re: [Dri-devel] dri driver features page -> website in CVS

2003-03-14 Thread Smitty
> You could set up a dummy database for testing? Yes I could, for teh meomnt I installed apache and php, apache works, php doesn't, if I get php working then I'll see about a database. > So, which files in doc/ should go into CVS? At a quick glance, only the > files in the doc/ directory itsel

Re: [Dri-devel] dri driver features page -> website in CVS

2003-03-14 Thread Nicholas Leippe
On Friday 14 March 2003 05:50 am, you wrote: > On Don, 2003-03-13 at 20:49, Smitty wrote: > > > > If I can do a CVS commit when I've been changing things on the webserver > > from the webserver that would be good. > > You can, but that should be the exception because otherwise the only > improvem

Re: [Dri-devel] dri driver features page -> website in CVS

2003-03-14 Thread Michel Dänzer
On Don, 2003-03-13 at 20:49, Smitty wrote: > > If I can do a CVS commit when I've been changing things on the webserver > from the webserver that would be good. You can, but that should be the exception because otherwise the only improvement over the current situation is that there's a backup in

Re: [Dri-devel] dri driver features page -> website in CVS

2003-03-13 Thread Smitty
> 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 direct

Re: [Dri-devel] dri driver features page -> website in CVS

2003-03-13 Thread Smitty
> Maybe this is a radical proposal, but it's a thing I've made good > experience with, over the last few months. > > http://twiki.org > > It is probably not the right thing if you want a perfectly styled > corporate web site. But it is an easy way for everybody to keep > documentation up-to-date

Re: [Dri-devel] dri driver features page -> website in CVS

2003-03-13 Thread Felix Kühling
Maybe this is a radical proposal, but it's a thing I've made good experience with, over the last few months. http://twiki.org It is probably not the right thing if you want a perfectly styled corporate web site. But it is an easy way for everybody to keep documentation up-to-date. The documents a

Re: [Dri-devel] dri driver features page -> website in CVS

2003-03-13 Thread Michel Dänzer
On Don, 2003-03-13 at 16:05, Smitty wrote: > > > > I'd rather not use CVS myself just for the website, when I mess up a > > > single character I just ssh onto the webserver and use vi to change > > > it. > > > > > > Also when something is being considered I like to test it / play with > > > and

Re: [Dri-devel] dri driver features page -> website in CVS

2003-03-13 Thread Smitty
> We don't need to put everything into CVS right away, but the way several > people are editing the same files right now is dangerous. Somewhat, at least it makes life interesting. > > I'd rather not use CVS myself just for the website, when I mess up a > > single character I just ssh onto the

Re: [Dri-devel] dri driver features page -> website in CVS

2003-03-12 Thread Michel Dänzer
On Mit, 2003-03-12 at 23:15, Smitty wrote: > > > PS: Editing files like this makes me kind of nervous, we should really > > > work out a way to handle the website in CVS. > > > > What's the difficulty in having it in CVS? it's extremely trivial to set > > up, you just tell the web server to cvs up

[Dri-devel] dri driver features page -> website in CVS

2003-03-12 Thread Smitty
> > PS: Editing files like this makes me kind of nervous, we should really > > work out a way to handle the website in CVS. > > What's the difficulty in having it in CVS? it's extremely trivial to set > up, you just tell the web server to cvs up from the repository every few > hours or so. The we