Re: Info about tags
Nick Patavalis wrote: Is there any way to get, via a script of something, information about the tags in a CVS-controlled tree? I want for example to answer the questions like the following: What tags exist, listed in chronological order? What are the names of the tags corresponding to vendor-branch imports, in chronological order? What tags exist in a specific branch? cvs status -v will provide much (all?) of the above. James etc /npat ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
changes getting clobbered--CVSREAD the culprit?
Hi all: I have worked on two projects under cvs control, one at school(3 developers) and my current work situation (3-4 developers). Our problem is that we are finding that changes are routinely getting clobbered when 2 developers work on the same file. We have a strict regimen (I hope) of always running "cvs update" before committing any changes. The wierd thing is, on my previous project, we never lost one line of code. The only difference in configuration between the two projects is that, at my work now, we have CVSREAD set, which means that cvs update pulls down files read-only, and we must use "cvs edit filename" before working on a file. All developers have been encouraged to check if a file is in use by another developer (using "cvs status" or "cvs editors") and general we're quite paranoid about not stepping on others' changes. But it still seems to happen, sometimes with quite frustrating results. My question, then, is twofold: can anybody see something that we are doing wrong? and, what are the benefits/drawbacks of setting CVSREAD? I zero in on this only because, as I said, it's the major config difference between the two projects, one of which was problem free and one which is not. Any input appreciated, James ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Bizarre update behaviour
Greetings: First, a bit of Changelog to illustrate my problem: 2002-03-11 17:50 jhughes * dps.pc (1.71): Added store_sig_repo message for use by fa 2002-03-06 16:22 jhughes * dps.pc (1.70): New message: get_dispatch_list 2002-02-15 14:46 jhughes * dps.pc (1.69): Fixed incorrect parameter bug in calls to query_*() functions My first problem is that the change in rev 1.69 has disappeared sometime between 1.69 and 1.71. I've posted before about code getting clobbered and basically been told it's human error, which I can buy, but still, it's mystifying how 3 successive changes by the same developer result in changes disappearing. However, what's more mystifying is what happened when I tried to restore the change that I had made in 1.69: doing this cvs up -r 1.69 resulted in 6 files with the message, *.c is no longer in the repository And not only that, but those same files had magically disappeared from the working directory. Repeated updates and a fresh checkout over the existing directory fail to pull them down again. However, creating a new directory and doing a fresh 'cvs co' pulled everything down as expected. Can anyone tell what I'm doing wrong? tia James -- James Hughes Esponsive Communications 613-549-3708 ext. 237 What is design?...It's where you stand with a foot in two worlds--the world of technology and the world of people and human purposes--and you try to bring the two together. Mitchell Kapor, A Software Design Manifesto ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Retaining execute permissions on scripts.
Hi all, I have some shell scripts that are executed from the working directory of one of the users in our system (Call it 'user X'). The problem I am having is that, if the scripts are modified and user X updates, the execute permissions are gone. CVSREAD is set, but I thought it would only affect write permissions. Is there a way to prevent this behaviour, short of wrapping 'cvs update' for user X in a script that will 'chmod +x' these scripts each time an update is performed? Thanks in advance for any insight. -- James Hughes Esponsive Communications 613-549-3708 ext. 237 ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Getting new directories on trunk-to-branch merge.
Hi, If I'm doing a merge, say, from trunk to branch, and new directories have been created on the trunk since the branch was made, is there a way to get those directories on the branch as well? I've tried "cvs up -d -j HEAD", but that didn't work; this implies to me that I have to re-add and re-commit the directories in order for branch and trunk to align. Is this correct? -- James Hughes Esponsive Communications ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Problems with file permissions
It sounds like you have the CVSREAD environment variable set, which causes files to be set read-only on update or checkout. If this is the case, you need to do "cvs edit " to get read-write permissions. Or, just unset CVSREAD and you won't have to worry about it. James Francis Hwang wrote: > Sorry, I don't think I was clear enough. What I mean is that when I open the > file in CVS, it gives me a read-only buffer: Those two % signs on the > bottom. > > But I'll go ask pcl-cvs. Thanks for the tip! > > Francis > > - Original Message - > From: "Derek Robert Price" <[EMAIL PROTECTED]> > To: "Francis Hwang" <[EMAIL PROTECTED]> > Cc: "Info CVS" <[EMAIL PROTECTED]> > Sent: Tuesday, August 13, 2002 11:05 AM > Subject: Re: Problems with file permissions > > > >>Francis Hwang wrote: >> >> >>>Basically, I open it in Emacs and Emacs won't let me edit it for some >>>CVS-related reason. >>> >>>Francis >>> >>> >> >>Nothing comes to mind. It might help if you could tell me the actual >>error message the machine prints. You mighc try the pcl-cvs email list >>too. pcl-cvs is the Emacs interfact to CVS. Check <http://cvshome.org> >>for the exact address of the pcl-cvs email list. >> >> > > > > > ___ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs > -- James Hughes Esponsive Communications 613-549-3708 ext. 237 ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
