Re: commitinfo stopped working!

2003-10-27 Thread Tom Marsh
Mark: Thanks for your quick reply! I probably mistated the problem somewhat. Using commitinfo in this way didn't stop anyone from adding bad directories, but it did stop them from adding files to those directories. But all that seems to have stopped working at all now. I don't even get the mes

Re: commitinfo stopped working!

2003-10-27 Thread Tom Marsh
Mark: Thanks for your quick reply! I probably mistated the problem somewhat. Using commitinfo in this way didn't stop anyone from adding bad directories, but it did stop them from adding files to those directories. But all that seems to have stopped working at all now. I don't even get the mes

Re: invalid changes error?

2003-10-27 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard Pfeiffer <[EMAIL PROTECTED]> writes: > > We tried to branch, but we got an error: "Invalid changes in file > database-deltas.sql". > I have never seen this before. > We didn't get it on the branch, actually; we got it on a checkout. This is

invalid changes error?

2003-10-27 Thread Richard Pfeiffer
  We tried to branch, but we got an error: "Invalid changes in file database-deltas.sql". I have never seen this before. We didn't get it on the branch, actually; we got it on a checkout. This is on branch rcom-10_5-branch. Any ideas?   Thanks! Do you Yahoo!? Exclusive Video Premiere - Britney S

Re: commitinfo stopped working!

2003-10-27 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tom Marsh <[EMAIL PROTECTED]> writes: > Dear info-cvs: > > Help! > > We're running cvs on HPUX, and built a good sized set of rules for > directories in commitinfo. All our developer connections come in > through pserver. > > commitinfo is someth

commitinfo stopped working!

2003-10-27 Thread Tom Marsh
Dear info-cvs: Help! We're running cvs on HPUX, and built a good sized set of rules for directories in commitinfo. All our developer connections come in through pserver. commitinfo is something like this: CVSROOT /usr/cvs/stuff/CVSROOT/allowcommit.sh XXBLAH.*/install /usr/cvs/stuff/CVSROO

Re: Multilevel vendor branch import

2003-10-27 Thread Rodolfo Schulz de Lima
On Mon, Oct 27, 2003 at 11:52:19AM -0800, Mark D. Baushke wrote: > CVS is a more mature product and needs to move a bit more conservatively > oriented when considering large changes in how it works. I suspect there > will be a place for cvs even after svn 1.0 is released. I know, it's easy to turn

Re: Multilevel vendor branch import

2003-10-27 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rodolfo Schulz de Lima <[EMAIL PROTECTED]> writes: > On Mon, Oct 27, 2003 at 01:22:23PM -0500, Greg A. Woods wrote: > > BTW, those are design limits, not bugs. They are caused by the way CVS > > tracks _the_ one vendor branch. The multiple vendor-br

Re: Multilevel vendor branch import

2003-10-27 Thread Rodolfo Schulz de Lima
On Mon, Oct 27, 2003 at 01:22:23PM -0500, Greg A. Woods wrote: > BTW, those are design limits, not bugs. They are caused by the way CVS > tracks _the_ one vendor branch. The multiple vendor-branch hacks I see, I've never considered them bugs. Just recently I 'discovered' subversion (svn), a cvs

Re: Multilevel vendor branch import

2003-10-27 Thread Greg A. Woods
[ On Sunday, October 26, 2003 at 12:59:48 (-0800), Mark D. Baushke wrote: ] > Subject: Re: Multilevel vendor branch import > > I have not tried to do it, but you might be able to use multiple vendor > branches by using the -b switch to import and then have the vendor be > LINUX_0_01, LINUX_0_10 '

CVS Feature Version 1.12.2 Released!

2003-10-27 Thread Derek Robert Price
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 CVS 1.12.2 has been released! This release contains new features as well as all the bug fixes from the stable release. This release fixes many bugs in CVS 1.12.1 and adds nifty new features, including experimental support for Pluggable Authentication