Thanks! ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 16, 2001 1:21 AM Subject: Info-cvs digest, Vol 1 #367 - 15 msgs > Send Info-cvs mailing list submissions to > [EMAIL PROTECTED] > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.gnu.org/mailman/listinfo/info-cvs > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Info-cvs digest..." > > > Today's Topics: > > 1. Re: reserved lock and other patches (Derek R. Price) > 2. Re: update -C (Larry Jones) > 3. Re: How to avoid propogation of changes (David H. Thornley) > 4. Re: reserved lock and other patches (Noel L Yap) > 5. CVS help (Paddy T) > 6. Re: reserved lock and other patches (Derek R. Price) > 7. Re: CVS help (Larry Jones) > 8. RE: How to avoid propogation of changes ([EMAIL PROTECTED]) > 9. Re: CVS help (Paddy T) > 10. CVS commits (Anand, Amit) > 11. Re: CVS commits (Larry Jones) > 12. Re: CVS help (Larry Jones) > 13. Re: CVS help (Paddy T) > 14. RE: info without working copy (Jerry Nairn) > 15. Web Site Traffic Building (TopTen) > > --__--__-- > > Message: 1 > Date: Thu, 15 Mar 2001 14:13:12 -0500 > From: "Derek R. Price" <[EMAIL PROTECTED]> > Organization: CollabNet > To: Noel L Yap <[EMAIL PROTECTED]> > CC: [EMAIL PROTECTED] > Subject: Re: reserved lock and other patches > > Noel L Yap wrote: > > > [EMAIL PROTECTED] on 2001.03.15 08:44:37 > > >Are these patched backwards/forwards compatible? i.e. what happens when the > > >client and server are out of synch on any of these patches? > > > > > >ME = multiple_edits, R = reservations, MER = multiple_edits+reservations, ! = > > not > > >present (pre-patch): > > > > > > Client Server Result > > > ---------- ---------- ---------- > > > ME !ME ??? > > > !ME ME ??? > > > R !R ??? > > > !R R ??? > > > MER !MER ??? > > > !MER MER ??? > > > > I remember testing for these situations when I originally made the patch. > > Nothing horrendous (ie crash or hang) happens, but I don't really remember > > exactly what happens (eg warning message, no message, ...). > > I think I'd want the commands to work. In other words, if the outputs of 'cvs > editors' and maybe other commands are incompatible/unparsable on one end or > another, the client/server command negotiation should allow for the version > discrepancy. I expect that the reservation code shouldn't be a severe problem > since either the server or client should reject the '-c' option and operation will > cease. > > > > Anyway, the new patches will have to be retested and I can say right now that I > > won't have the bandwidth to do so (and I haven't figured out exactly how to add > > to the regression test suite). So, ANY VOLUNTEERS? > > There's not room in the regression suite to test different client/server versions > outside, perhaps, of launching the executable as a server and fiddling with stdin > (see the pserver test), but the basic multiple_edits and reservations behavior > should be checked for. > > I'd also want to see documentation updates (to cvs.texinfo) before I'd check this > in. > > Derek > > -- > Derek Price CVS Solutions Architect http://CVSHome.org ) > mailto:[EMAIL PROTECTED] CollabNet ( http://collab.net ) > -- > I will not fake my way through life. > I will not fake my way through life. > I will not fake my way through life... > > - Bart Simpson on chalkboard, _The Simpsons_ > > > > > > --__--__-- > > Message: 2 > Subject: Re: update -C > To: [EMAIL PROTECTED] > Date: Thu, 15 Mar 2001 14:23:58 -0500 (EST) > Cc: [EMAIL PROTECTED] > From: [EMAIL PROTECTED] (Larry Jones) > > John D. Stein writes: > > > > In the command quick reference there is mention of a -C option for the > > update command. I need to get the file that is in the repository and > > overwrite the current working file, and it looks like the -C option > > would do that for me, but I get the following error: > > -C was new in CVS 1.11, I believe -- you're probably running an older > version. You can get the current version from www.cvshome.org. > > -Larry Jones > > I always have to help Dad establish the proper context. -- Calvin > > > --__--__-- > > Message: 3 > Date: Thu, 15 Mar 2001 13:22:40 -0600 > From: "David H. Thornley" <[EMAIL PROTECTED]> > Organization: CES International, Inc. > To: [EMAIL PROTECTED] > Subject: Re: How to avoid propogation of changes > > > > [EMAIL PROTECTED] wrote: > > > > At any given time, we have multiple releases of our software under > > development. Each release has it's own branch, with the latest release > > being developed on the trunk. We propogate changes downstream by doing > > merges from each release branch to the immediate downstream release > > branch. > > > > Here is the problem: What if we make a change that we don't want > > propogated downstream. Does any one know of a good way to accomplish > > this? > > > Um, don't propagate it? > > Seriously, CVS doesn't move propagate changes by itself, so you > must have some sort of mechanism to do so. This means you've > got to figure out how to optionally disable it. > > To give an example, we maintain _MERGED tags on our branches, so > BRANCH_3 would have an associated BRANCH_3_MERGED tag. We have > a Perl script that will merge from a branch to, say, head. > It merges everything from BRANCH_3_MERGED to BRANCH_3, and then > moves BRANCH_3_MERGED. This means that the way to avoid > propagating a change is to move BRANCH_3_MERGED past it, and > this is indeed what we do (I've got a Perl script for that, too, > for consistency, and it's pretty short.) > > -- > David H. Thornley Software Engineer > at CES International, Inc.: [EMAIL PROTECTED] or (763)-694-2556 > at home: (612)-623-0552 or [EMAIL PROTECTED] or > http://www.visi.com/~thornley/david/ > > > --__--__-- > > Message: 4 > From: "Noel L Yap" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > cc: [EMAIL PROTECTED] > Date: Thu, 15 Mar 2001 14:36:14 -0500 > Subject: Re: reserved lock and other patches > > > > > > [EMAIL PROTECTED] on 2001.03.15 14:13:12 > >> I remember testing for these situations when I originally made the patch. > >> Nothing horrendous (ie crash or hang) happens, but I don't really remember > >> exactly what happens (eg warning message, no message, ...). > > > >I think I'd want the commands to work. In other words, if the outputs of 'cvs > >editors' and maybe other commands are incompatible/unparsable on one end or > >another, the client/server command negotiation should allow for the version > >discrepancy. I expect that the reservation code shouldn't be a severe problem > >since either the server or client should reject the '-c' option and operation > will > >cease. > > Oh, yes, that's right, if either the client or the server doesn't support "-c", > the operation won't go through. > > IIRC, "cvs editors" will work regardless of who supports multiple edits since > the client will first check to see if the server supports the feature. In the > end, "cvs edit" just stores some info in CVS/fileattr. This info is parsed and > outputted by "cvs editors". > > > >> Anyway, the new patches will have to be retested and I can say right now that > I > >> won't have the bandwidth to do so (and I haven't figured out exactly how to > add > >> to the regression test suite). So, ANY VOLUNTEERS? > > > >There's not room in the regression suite to test different client/server > versions > >outside, perhaps, of launching the executable as a server and fiddling with > stdin > >(see the pserver test), but the basic multiple_edits and reservations behavior > >should be checked for. > > I agree. Any volunteers? > > >I'd also want to see documentation updates (to cvs.texinfo) before I'd check > this > >in. > > It looks like cvs.texinfo is easy enough to change, but can you tell me how I > can test those changes? > > Thanks, > Noel > > > > This communication is for informational purposes only. It is not intended as > an offer or solicitation for the purchase or sale of any financial instrument > or as an official confirmation of any transaction. All market prices, data > and other information are not warranted as to completeness or accuracy and > are subject to change without notice. Any comments or statements made herein > do not necessarily reflect those of J.P. Morgan Chase & Co., its > subsidiaries and affiliates. > > > > --__--__-- > > Message: 5 > Date: Thu, 15 Mar 2001 11:47:36 -0800 (PST) > From: Paddy T <[EMAIL PROTECTED]> > Subject: CVS help > To: [EMAIL PROTECTED] > > Hi > > We are having a problem with CVS.We changed the group > to which the CVSROOT files belonged.But we also put > all the developers in the same group.Still when we try > remote check out it is giving error Permission > denied.Initially it gave the error permission to > history file is denied.But once we put them in the > same group,it is giving the above error.we use :server > and rsh is working. > Pls help with this > Thanks, > Paddy Thomas > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Auctions - Buy the things you want at great prices. > http://auctions.yahoo.com/ > > > --__--__-- > > Message: 6 > Date: Thu, 15 Mar 2001 15:00:17 -0500 > From: "Derek R. Price" <[EMAIL PROTECTED]> > Organization: CollabNet > To: Noel L Yap <[EMAIL PROTECTED]> > CC: [EMAIL PROTECTED] > Subject: Re: reserved lock and other patches > > Noel L Yap wrote: > > > Oh, yes, that's right, if either the client or the server doesn't support "-c", > > the operation won't go through. > > > > IIRC, "cvs editors" will work regardless of who supports multiple edits since > > the client will first check to see if the server supports the feature. In the > > end, "cvs edit" just stores some info in CVS/fileattr. This info is parsed and > > outputted by "cvs editors". > > That sounds like about what I was hoping for. > > > > >I'd also want to see documentation updates (to cvs.texinfo) before I'd check > > this > > >in. > > > > It looks like cvs.texinfo is easy enough to change, but can you tell me how I > > can test those changes? > > $ cd doc > $ make info > > Should rebuild the info files. You need makeinfo and probably a Tex distribution > installed. TeTeX is pretty good, IMANAQSHAIPSBO, and, IIRC, it comes with > makeinfo. Then just use > > $ info --directory=. --file=cvs.info > > and page through the info file to the sections you want to examine. > > Derek > -- > Derek Price CVS Solutions Architect http://CVSHome.org ) > mailto:[EMAIL PROTECTED] CollabNet ( http://collab.net ) > -- > Once Law was sitting on the bench > And Mercy knelt a-weeping. > "Clear out!" he cried, "disordered wench! > Nor come before me creeping. > Upon you knees if you appear, > 'Tis plain you have no standing here." > > Then Justice came. His Honor cried: > "YOUR states? -- Devil seize you!" > "Amica curiae," she replied -- > "Friend of the court, so please you." > "Begone!" he shouted -- "There's the door -- > I never saw your face before!" > -- Ambrose Bierce, "The Devil's Dictionary" > > > > > --__--__-- > > Message: 7 > Subject: Re: CVS help > To: [EMAIL PROTECTED] (Paddy T) > Date: Thu, 15 Mar 2001 15:19:04 -0500 (EST) > Cc: [EMAIL PROTECTED] > From: [EMAIL PROTECTED] (Larry Jones) > > Paddy T writes: > > > > We are having a problem with CVS.We changed the group > > to which the CVSROOT files belonged.But we also put > > all the developers in the same group.Still when we try > > remote check out it is giving error Permission > > denied.Initially it gave the error permission to > > history file is denied.But once we put them in the > > same group,it is giving the above error.we use :server > > and rsh is working. > > It would be helpfull to see the exact command and the exact error > message. > > -Larry Jones > > ...That would be pretty cool, if they weren't out to kill me. -- Calvin > > > --__--__-- > > Message: 8 > From: [EMAIL PROTECTED] > Date: Thu, 15 Mar 2001 15:06:03 -0600 > Subject: RE: How to avoid propogation of changes > TO: [EMAIL PROTECTED], [EMAIL PROTECTED] > > > --openmail-part-21b7f99c-00000001 > Content-Type: text/plain; charset=US-ASCII > Content-Disposition: inline > ;Creation-Date="Thu, 15 Mar 2001 15:06:03 -0600" > Content-Transfer-Encoding: 7bit > > > > > [EMAIL PROTECTED] wrote: > > > > > > At any given time, we have multiple releases of our software under > > > development. Each release has it's own branch, with the > > latest release > > > being developed on the trunk. We propogate changes > > downstream by doing > > > merges from each release branch to the immediate downstream release > > > branch. > > > > > > Here is the problem: What if we make a change that we don't want > > > propogated downstream. Does any one know of a good way to accomplish > > > this? > > > > > Um, don't propagate it? > > > > Seriously, CVS doesn't move propagate changes by itself, so you > > must have some sort of mechanism to do so. This means you've > > got to figure out how to optionally disable it. > > To give an example, we maintain_MERGED tags on our branches, so > > BRANCH_3 would have an associated BRANCH_3_MERGED tag. > > We do the same thing. > > > We have > > a Perl script that will merge from a branch to, say, head. > > It merges everything from BRANCH_3_MERGED to BRANCH_3, and then > > moves BRANCH_3_MERGED. > > > This means that the way to avoid > > propagating a change is to move BRANCH_3_MERGED past it, and > > this is indeed what we do (I've got a Perl script for that, too, > > for consistency, and it's pretty short.) > > This would require us to merge all of our files individually, whereas > we merge the entire branch in a single command, i.e. update is invoked > at the top level directory with no file args. Given that our > application has over 3000 files, merging each file individually might > not be tenable. This is an interesting idea though.\ > > Please let me know if I've missing something in what you have said. > And, thanks. > > Chuck > > --openmail-part-21b7f99c-00000001-- > > > > --__--__-- > > Message: 9 > Date: Thu, 15 Mar 2001 13:08:52 -0800 (PST) > From: Paddy T <[EMAIL PROTECTED]> > Subject: Re: CVS help > To: Larry Jones <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > > Hi > when we give > cvs co Mbtv > It says > Permission Denied > But when I give > cvs -d /cvsadmin/rep co Mbtv > then it says > cvs [checkout aborted]: /cvsadmin/rep/CVSROOT: No > such file or directory > I checked the permissions to the history file and it > is fine.As I wrote before rsh is working fine. > I just don't understand why this is giving error. > Thanks in advance, > Paddy Thomas > --- Larry Jones <[EMAIL PROTECTED]> wrote: > > Paddy T writes: > > > > > > We are having a problem with CVS.We changed the > > group > > > to which the CVSROOT files belonged.But we also > > put > > > all the developers in the same group.Still when we > > try > > > remote check out it is giving error Permission > > > denied.Initially it gave the error permission to > > > history file is denied.But once we put them in the > > > same group,it is giving the above error.we use > > :server > > > and rsh is working. > > > > It would be helpfull to see the exact command and > > the exact error > > message. > > > > -Larry Jones > > > > ...That would be pretty cool, if they weren't out to > > kill me. -- Calvin > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Auctions - Buy the things you want at great prices. > http://auctions.yahoo.com/ > > > --__--__-- > > Message: 10 > From: "Anand, Amit" <[EMAIL PROTECTED]> > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > Subject: CVS commits > Date: Thu, 15 Mar 2001 16:34:33 -0500 > > I connect to CVS in the pserver mode from a windows machine using WinCvs. > The commits don't work. I get the following error message > > cvs server: cannot exec rcs: No such file or directory > cvs server: cannot change branch to default for > /home/aanand/CVSD/newrepos/CVSTest/src/cvstest/Frame1.java,v > cvs server: cannot exec rcs: No such file or directory > cvs server: could not unlock > /home/aanand/CVSD/newrepos/CVSTest/src/cvstest/Frame1.java,v > > Thank you for your help. > > Regards > > Amit Anand > > > -------------------------------------------------------------------------- ---- > This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers Inc. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. > > > > > --__--__-- > > Message: 11 > Subject: Re: CVS commits > To: [EMAIL PROTECTED] (Anand, Amit) > Date: Thu, 15 Mar 2001 17:03:55 -0500 (EST) > Cc: [EMAIL PROTECTED] > From: [EMAIL PROTECTED] (Larry Jones) > > Anand, Amit writes: > > > > cvs server: cannot exec rcs: No such file or directory > > cvs server: cannot change branch to default for > > /home/aanand/CVSD/newrepos/CVSTest/src/cvstest/Frame1.java,v > > cvs server: cannot exec rcs: No such file or directory > > cvs server: could not unlock > > /home/aanand/CVSD/newrepos/CVSTest/src/cvstest/Frame1.java,v > > Your CVS server is ancient. Try upgrading to the current version (1.11) > which you can find at www.cvshome.org. > > -Larry Jones > > My "C-" firmly establishes me on the cutting edge of the avant-garde. > -- Calvin > > > --__--__-- > > Message: 12 > Subject: Re: CVS help > To: [EMAIL PROTECTED] (Paddy T) > Date: Thu, 15 Mar 2001 17:18:12 -0500 (EST) > Cc: [EMAIL PROTECTED] > From: [EMAIL PROTECTED] (Larry Jones) > > Paddy T writes: > > > > when we give > > cvs co Mbtv > > It says > > Permission Denied > > If that's really all it says, then the problem is most likely that your > repository is missing the CVSROOT/Emptydir directory (or it has really > funky permissions). Also, what version of CVS is the server? If it > isn't 1.11, I strongly suggest you upgrade. (I know I fixed the error > logic so that you get a real error message instead of just "Permission > denied", and I'm pretty sure that was before 1.11, but I could be > wrong.) > > -Larry Jones > > I wonder what's on TV now. -- Calvin > > > --__--__-- > > Message: 13 > Date: Thu, 15 Mar 2001 14:39:32 -0800 (PST) > From: Paddy T <[EMAIL PROTECTED]> > Subject: Re: CVS help > To: Larry Jones <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > > Hi > My server version is 1.10.7. > There is an Emptydir/drivers/block with > ll_rw_blk.c,v file in it.Should this file have r/w > access for users in the group for them to be able to > checkout?Now it has only read access for user,owner > and group.Pls clarify. > > Thanks a lot, > Paddy Thomas > > --- Larry Jones <[EMAIL PROTECTED]> wrote: > > Paddy T writes: > > > > > > when we give > > > cvs co Mbtv > > > It says > > > Permission Denied > > > > If that's really all it says, then the problem is > > most likely that your > > repository is missing the CVSROOT/Emptydir directory > > (or it has really > > funky permissions). Also, what version of CVS is > > the server? If it > > isn't 1.11, I strongly suggest you upgrade. (I know > > I fixed the error > > logic so that you get a real error message instead > > of just "Permission > > denied", and I'm pretty sure that was before 1.11, > > but I could be > > wrong.) > > > > -Larry Jones > > > > I wonder what's on TV now. -- Calvin > > > __________________________________________________ > Do You Yahoo!? > Get email at your own domain with Yahoo! Mail. > http://personal.mail.yahoo.com/ > > > --__--__-- > > Message: 14 > From: Jerry Nairn <[EMAIL PROTECTED]> > To: "'Largent, Jim'" <[EMAIL PROTECTED]>, "'[EMAIL PROTECTED]'" > <[EMAIL PROTECTED]> > Subject: RE: info without working copy > Date: Thu, 15 Mar 2001 18:55:34 -0800 > > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > > ------_=_NextPart_001_01C0ADC4.923E5E10 > Content-Type: text/plain; > charset="iso-8859-1" > > There's a trick you can do with rdiff, to discover the head revision or the > revision that a certain tag is on. > cvs -n -q rdiff -l -s -r 0 $Repository/$FileName > cvs -n -q rdiff -l -s -r $TagToMatch $Repository/$FileName > That's about it. > Jerry > > >From: Largent, Jim [mailto:[EMAIL PROTECTED]] > >Sent: Thursday, March 15, 2001 5:17 AM > > >Is there some trick to getting information similar to cvs log without a > >working copy? I have several Perl scripts that I used with > > ------_=_NextPart_001_01C0ADC4.923E5E10 > Content-Type: text/html; > charset="iso-8859-1" > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> > <HTML> > <HEAD> > <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> > <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12"> > <TITLE>RE: info without working copy</TITLE> > </HEAD> > <BODY> > > <P><FONT SIZE=2>There's a trick you can do with rdiff, to discover the head revision or the revision that a certain tag is on.</FONT> > <BR><FONT SIZE=2>cvs -n -q rdiff -l -s -r 0 $Repository/$FileName</FONT> > <BR><FONT SIZE=2>cvs -n -q rdiff -l -s -r $TagToMatch $Repository/$FileName</FONT> > <BR><FONT SIZE=2>That's about it.</FONT> > <BR><FONT SIZE=2>Jerry</FONT> > </P> > > <P><FONT SIZE=2>>From: Largent, Jim [<A HREF="mailto:[EMAIL PROTECTED]">mailto:[EMAIL PROTECTED]</A>]</FONT> > <BR><FONT SIZE=2>>Sent: Thursday, March 15, 2001 5:17 AM</FONT> > </P> > > <P><FONT SIZE=2>>Is there some trick to getting information similar to cvs log without a</FONT> > <BR><FONT SIZE=2>>working copy? I have several Perl scripts that I used with </FONT> > </P> > > </BODY> > </HTML> > ------_=_NextPart_001_01C0ADC4.923E5E10-- > > > --__--__-- > > Message: 15 > From: <Top Ten> > To: <[EMAIL PROTECTED]> > Subject: Web Site Traffic Building > Date: Fri, 16 Mar 2001 01:16:56 -0500 > > This is a multi-part message in MIME format. > > --Z_MULTI_PART_MAIL_BOUNDAEY_S > Content-Type: text/plain > Content-Transfer-Encoding: base64 > > V2UgaGF2ZSByYW5rZWQgdGhlIHRvcCB0ZW4gdHJhZmZpYyBidWlsZGluZyBzaXRlcyBvbiB0 > aGUgd2ViLCB0aGVzZSBzaXRlcw0KaGF2ZSBiZWVuIHJhbmtlZCBieSBvdXIgZXhwZXJ0cywg > b3VyIGNsaWVudHMgYW5kIGJ5IHlvdSBvdXIgdmlzaXRvcnMuIENvbWUNCnRvICB3d3cuZ3Jl > YXRmcmVlc2l0ZS5uZXQvYmVzdHRlbg0KDQpPbmUgb2YgdGhlIHRvcCB0ZW4gc2l0ZXMsIGNh > biBldmVuIGd1YXJhbnRlZSB0b3AgcGxhY2VtZW50IG9uIHRoZSB0b3AgdGVuDQpzZWFyY2gg > ZW5naW5lcy4NCg0KT3VyIHNpdGUgaGFzIGJlZW4gZGV2ZWxvcGVkIHRvIGhlbHAgeW91IGZp > bmQgdGhlIG1vc3QgY29zdC1lZmZlY3RpdmUgdHJhZmZpYw0Kb24gdGhlIHdlYi4gUGxlYXNl > IGZlZWwgZnJlZSB0byBjb250YWN0IHVzIHdpdGggYW55IHF1ZXN0aW9ucy4gICAg > --Z_MULTI_PART_MAIL_BOUNDAEY_S-- > > > > --__--__-- > > _______________________________________________ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs > > > End of Info-cvs Digest _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
