RE: [boost] Re: CVS status

2003-05-08 Thread Aleksey Gurtovoy
Beman Dawes wrote: > > ... various backup suggestions > > SourceForge already makes the entire Boost CVS tarball available every > night, and several Boosters download it daily. Oh, good. There is no such thing as too much backup. > (At least I hope they do - I have no way of telling if they a

Re: [boost] Re: CVS status

2003-05-08 Thread Beman Dawes
> ... various backup suggestions SourceForge already makes the entire Boost CVS tarball available every night, and several Boosters download it daily. (At least I hope they do - I have no way of telling if they are still running their cron jobs.) That is supposed to protect us from total failu

Re: [boost] Re: CVS status

2003-05-08 Thread Vladimir Prus
Gennaro Prota wrote: > >I think this is a bit more complicated that it should be. Why don't just > >create boost-wide commit emails mailing list? > > Off-hand _this one_ seems more complicated, because it involves more > people than necessary and forces to keep the diffs (though just for, > say, a

Re: [boost] Re: CVS status

2003-05-08 Thread Aleksey Gurtovoy
Gennaro Prota wrote: > Thanks Aleksey. I was particularly interested to stlport.hpp > (incidentally: though that doesn't affect the good functioning of the > file, the space between # and endif: > > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost/boost/boost/config/stdl ib/stlport.hpp.diff?r1=