Re: CVS For VMS
Martin Eismann [EMAIL PROTECTED] on 07/09/2001 10:01:10 PM To: [EMAIL PROTECTED] cc: (bcc: Rex Jolliff/YM/RWDOE) Subject: Re: CVS For VMS Federal Record Status Not Determined Hello dear list-members! I am very interested getting an OpenVMS-Alpha-binary (maybe client and server? would be great!!). Upper mentioned wildcard-support would be excellent... Has anybody compiled/linked a OpenVMS-Client from actual sources? I have linked CVS v1.11 on an Alpha (DEC C V5.7-006 on OpenVMS Alpha V7.2-1). Only the client will build. I remember sending this version to the CVS maintainers for distribution. If I get some time I'll build 1.11.1p1 and send in to them also. Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Upgrading CMS
Even though this is not a CMS mailing list. Try this from the 'Ask the Wizard' site at compaq: http://www.openvms.compaq.com/wizard/wiz_0170.html The Question is: i WOULD lIKE to upgrade from cms version 3.5-2 to 3.9 the convert utility enables convert from v2 to v3 The Answer is: To convert from CMS V3.5-03 or earlier to CMS V3.5-05 or later: $ RENAME disk:[directory]00CMS.* 01CMS.* $ COPY NLA0: disk:[directory]00CMS.CMS Make certain the newly-creted (empty) 00CMS.CMS file has the same protection as the existing (but recently renamed) 01CMS.CMS file. No other conversion steps are required. [EMAIL PROTECTED] on 05/24/2001 03:23:11 PM To: [EMAIL PROTECTED] cc: (bcc: Rex Jolliff/YM/RWDOE) Subject: Upgrading CMS Federal Record Status Not Determined Help, I have a VAX/VMS V5.5-2 server renning DEC/CMS Version V3.5-5. We have upgraded to an Alpha Operating System Version V7.2-1 with CMS Version V4.0. I am unable to convert the data in the V3.5-5 to the V4.0 CMS. The error I receive is as follows: |...DCS=cms CMS set lib [tra_cms.sits_lib] %CMS-E-NOREF, error referencing [TRA_CMS.SITS_LIB] -CMS-E-MANCONLIB, $1$DGA20:[TRA_CMS.SITS_LIB] is prior to CMS V3.5-04 library and cannot be used with the current version. %CMS-W-UNDEFLIB, library is undefined CMS sho element %CMS-E-NOREF, error referencing LOCATION:[TRA_CMS.MEMO_LIB] -CMS-E-MANCONLIB, LOCATION:[TRA_CMS.MEMO_LIB] is prior to CMS V3.5-04 library and cannot be used with the current version. %CMS-W-NOELE, no elements found CMS |...DCS=cms CMS set lib [tra_cms.sits_lib] %CMS-E-NOREF, error referencing [TRA_CMS.SITS_LIB] -CMS-E-MANCONLIB, $1$DGA20:[TRA_CMS.SITS_LIB] is prior to CMS V3.5-04 library and cannot be used with the current version. %CMS-W-UNDEFLIB, library is undefined CMS sho element %CMS-E-NOREF, error referencing LOCATION:[TRA_CMS.MEMO_LIB] -CMS-E-MANCONLIB, LOCATION:[TRA_CMS.MEMO_LIB] is prior to CMS V3.5-04 library and cannot be used with the current version. %CMS-W-NOELE, no elements found CMS Can this be fixed and how can I do it??? Fred ___ 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
Re: $Name$ Keyword does not expand
Try using the 'export' command. The idea, I think, is that with a checkout you might be temped to modify the code thus invalidating the Name keyword, whereas with an export it is explicit that you should not furthur modify the code. Rex. Markus Grunwald [EMAIL PROTECTED] on 04/25/2001 12:57:52 AM To: [EMAIL PROTECTED] cc: (bcc: Rex Jolliff/YM/RWDOE) Subject: $Name$ Keyword does not expand Federal Record Status Not Determined Hi there ! I would like to use the $Name$ Keyword in my java source. To do this, I added the line: public final static String cvsRelease = new String($Name$); to my source. Then, I tagged it prerelease-1_0. To get the substitution, I executed cvs -d :pserver:grunwalm@swscvs1:/usr/local/cvsroot checkout -r prerelease-1_0 UserAccount but the line just expanded to public final static String cvsRelease = new String($Name: $); I thought, there should stand $Name: prerelease-1_0$ ??? Other tags ($id$...) work just fine. The log says, the tag is there: grunwalm@winlinux1: cvs -d :pserver:grunwalm@swscvs1:/usr/local/cvsroot log UserAccount/src/com/somewhere/frames/AboutBox.java RCS file: /usr/local/cvsroot/UserAccount/src/com/somewhere/frames/AboutBox.java,v Working file: UserAccount/src/com/somewhere/frames/AboutBox.java head: 1.4 branch: locks: strict access list: symbolic names: prerelease-1_0: 1.4 keyword substitution: kv total revisions: 4; selected revisions: 4 description: I dont' know what to do. I had the same problem at home and ignored it after a while, but here at work it is urgent... Many thanks in advance, -- Markus Grunwald Registered Linux User Nr 101577 PGP Key: http://counter.li.orghttp://www.grunwald.2xs.de ___ 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
Re: CVS from RCS?
Id like to add that if I remember correctly, it is possible to create RCS files that will not be usable in CVS. For one example, if you have revisions of the form 1.x.y.z then is it not the case that these will confuse CVS? Rex. [EMAIL PROTECTED] (Larry Jones) on 04/16/2001 11:41:09 AM To: [EMAIL PROTECTED] (Andy Bradford) cc: [EMAIL PROTECTED](bcc: Rex Jolliff/YM/RWDOE) Subject: Re: CVS from RCS? Federal Record Status Not Determined Andy Bradford writes: I have a few files that are currently managed via RCS, however, I would like to put them into a CVS repository. Will this be as simple as copying the ,v files into the directory or will I need to do something more complicated? I would like to retain all the version change information if possible. It's as simple as copying the ,v files into the repository directory. -Larry Jones If I was being raised in a better environment, I wouldn't do things like that. -- Calvin ___ 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
Re: -t/-f in cvswrappers
DAve Goodrich [EMAIL PROTECTED] on 04/13/2001 12:03:25 PM To: Larry Jones [EMAIL PROTECTED] cc: [EMAIL PROTECTED](bcc: Rex Jolliff/YM/RWDOE) Subject: Re: -t/-f in cvswrappers Federal Record Status Not Determined on 4/12/01 4:36 PM, Larry Jones at [EMAIL PROTECTED] wrote: DAve Goodrich writes: Hello all. I'm running into a problem with clients that send files to the repository with Mac or Win file endings. What clients are these? It is the client's responsibility to convert text files from whatever the local line ending convention is to the canonical line-feed termination before sending them to the server. If that isn't happening, the clients are buggy or misconfigured. We have several people using MacCVSClient, which uses Mac line endings by default. The developer knows that people who are creating code that must eventually live on a Unix box(web pages) have a problem with this (me) and he is working to remedy that. the line endings should get translated by the client. If they are not being translated, then there is a problem with that client. Perhaps it is misconfigured. You aren't using some kind of shared file system and trying to commit files from a different platform than the one you're running on, are you? Nope creating web pages on Mac/Windows and serving from Unix. I do not think you understood his question. Are you using the pserver method, the rsh/ssh method or a shared drive to access the cvs repository. If you are using a shared drive, then this is your problem. But I get an error that "cvs [server aborted]: -t/-f wrappers not supported by this version of CVS" There were bugs in the -t/-f wrapper code that could cause silent loss Thanks, not what I wanted to hear, but oh well. Seems that would be an extremely useful function. I would like to be able to filter many things through a file prior to committing, check for common copyright code at the bottom of a file, check for tags ($RCSfile$) at the beginning of each file, things I must do weekly in code review. Odd it seems to have been forgotten so long. All these things can be done using a trigger script placed in the commitinfo file. Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Issues with raising the 'floor' in CVS
This means that the data wasn't checked out of CVS in the first place. Importcheckout or add the files before attempting a checkin. This points out an weakness (or at least a perceived one) in CVS in my opinion. There isn't an easy way to add a new 'module' to the repository. Either you use import, which doesnt necessarily make sence if you're a developer of original code and there is no vendor, or you use the trick of checking out the root non-recursively and adding every file in the new subtree. I would propose the following: add an option to add (or commit) called --new or something like that that allows someone to add a top level directory and recurse into it adding subdirs. This option should check to insure that none of the files in the requested add operation exist in the repository and fail if they do. also this command should probably prevent people from adding files to the root of the repository, or to the CVSROOT dir. an example: $ ls hexdump/ tmp/ $ cvs -d /data/cvs/repo add --new hexdump Created directory hexdump Added file hexdump.c Added file Makefile Created directory hexdump/debug $ Comments are inevitable i'm sure. ;) Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: cvs add --new
Actually I comment was meant to point out a percieved flaw in CVS. When I show developers CVS in the environment that I work, putting new projects into CVS is always a place that they see weakness in CVS as they either have to pretend they are their own vendor, or use the top level dir checkout trick. I was simply suggesting that we can improve the image of CVS by adding an easy way for a user to create a new top level directory for a new subsystem. Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Multiple Repositories on a server
just use two --allow-root command line parameters Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Viewing and Committing Older Revision in WinCVS
To: [EMAIL PROTECTED] cc: (bcc: Rex Jolliff/YM/RWDOE) Subject: Viewing and Committing Older Revision in WinCVS I have just started to use WinCVS and have a couple of questions regarding WinCVS. 1.) Is there a way to view the older revision of a file without checking out that particular revision? yes: cvs co -p -rx.x foo.c 2.) How do you commit the previous revision of a file back into repository and make that file the latest revision? I tried to do it but it won't let me replace the latest revision with the older revision? cvs co -p -rx.x foo.c foo.c cvs commit foo.c -m "step on bob's efforts" I'd appreciate your help. -Lek- No problem Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Problems with CVS version 1.10.8 on Windows 2000
My guess would be that the colon in the pathname is being interpreted as a field separator. Try the following: cvs -d :local:\\z\iil\iswp\data\apt\ISIS\repository get trycvs "Reinstein, Shlomo" [EMAIL PROTECTED] on 01/30/2001 10:29:44 PM To: "'[EMAIL PROTECTED]'" [EMAIL PROTECTED], "Reinstein, Shlomo" [EMAIL PROTECTED] cc: [EMAIL PROTECTED](bcc: Rex Jolliff/YM/RWDOE) Subject: RE: Problems with CVS version 1.10.8 on Windows 2000 Federal Record Status Not Determined Hi, I forgot to say that in my previous email - I also tried it with forward slashes (after reading in the mailing-list about similar problems): cvs -d :local:z:/iil/iswp/data/apt/ISIS/repository get trycvs Doesn't work either - I get the very same error message from CVS. Please note that, like I said in the previous email, the same command-line (even with backward-slashes) works with version 1.10.7 of CVS. Shlomo -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 30, 2001 6:12 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Problems with CVS version 1.10.8 on Windows 2000 Reinstein, Shlomo writes: What can the problem be? Isn't z:\iil\... an absolute pathname? No, it's not. There are some parts of CVS that insist on forward slashes (/) instead of backward slashes (\) and this is one of them. I understand that this is inconvenient for Windows users, but I urge you to get used to using forward slashes with CVS or you'll have no end of strange problems. -Larry Jones That's one of the remarkable things about life. It's never so bad that it can't get worse. -- Calvin ___ 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
Re: -kb
I think the file should contain regex's not file wildcards, and I believe that the first line to be matched is used, so probably something like the following: --- .*\.[Hh][Tt][Mm][Ll] -k 'v' .* -k 'b' Rob Helmer [EMAIL PROTECTED] on 01/27/2001 12:40:01 AM To: [EMAIL PROTECTED] cc: (bcc: Rex Jolliff/YM/RWDOE) Subject: -kb Federal Record Status Not Determined Hello, If I would like to have a repository that contains all binaries except for one extension ( .html for instance ), is the proper way to specify that something like excerpt from cvswrappers * -k 'b' *.[Hh][Tt][Mm][Ll] -k 'v' /excerpt from cvswrappers ( I am not sure on that -kv option.. ) Is this doable? If not, can I at least do the * -k 'b' line and get away with it? Should I do [A-Za-z0-9] or something like that instead? I couldn't find help for this on cvshome, any info is appreciated.. Thanks -- Rob Helmer ___ 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
Re: Question on disabling automatic merges
If you mean that you want to stop a developer from taking an old copy of a file and checking it in over the top of the current version of the file, there is a set of scripts in contrib directory that will facilitate this. They will require you to have $Id$ markers at the top of every file though, and it would still be possible for developers to fool the scripts, just not easy. Rex. Teala Spitzbarth [EMAIL PROTECTED] on 01/24/2001 04:09:40 PM To: [EMAIL PROTECTED] cc: (bcc: Rex Jolliff/YM/RWDOE) Subject: Question on disabling automatic merges Federal Record Status Not Determined Hi Folks, Is there anyway to disable the automatic merge on checkin under CVS? I.e. to force that if a developer tries to checkin a file from a working copy that is outdated - they get an error message? I can see that if you admin files with the -m option, it will be disabled, but this requires some overhead. I was just wondering if I was missing an easier configuration option. Thanks much, Teala [EMAIL PROTECTED] ___ 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
Re: Tags in keyword substitutions
I should point out that $Name$ only works if you checkout or export based on a tag. But, this is the only way you should be building release candidates anyway. Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: file access
Guus Writes: PiAgLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gIEZyb206IGluZm8tY3ZzLWFkbWluQGdu dS5vcmcgDQo+ICBbbWFpbHRvOmluZm8tY3ZzLWFkbWluQGdudS5vcmddT24gQmVoYWxmIE9mDQo+ [...] Ya dont say. Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS Problem
You Wrote: I'm having trouble using CVS. I will check out files, edit them, and commit them. It gives them a new version number (no error comes up), but the files are not updated. If I go to the CVS repository and look at the file there, it's the old version not the one I just modified. Has anyone seen this before? Your respository (with the exception of the CVSROOT control directory) should only contain version control files (files that end with ,v). If you are looking in the repository and seeing normal files only, then you are not looking in the respostory. If you are seeing both version controlled files and normal files, then either someone has checked out the repository on top of itself, or someone has copied the normal files on top of the repository structure, and neither of these things were a good idea. Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Multiple developers in one work area
Tony Wrote: I've a new CVS user but an old hand at DEC's CMS code management system. The latter was very good about allowing multiple people in one area. CVS isn't so strong there. In my opinion this is basically bunk. CMS is roughly equivalent to RCS, and in the same vein supports the locking development philosophy. From my memory there is nothing magical about CMS's support for multiple developers working out of the same developement directory. I think it is because old-tyme Unix hacks tended to be lone programmers working on smaller projects and therefore didn't need a strong cooperative system. CVS was born because programs were getting more complex and the more traditional businesses were beginning to use Unix. In this Brave New Environment, however, the lone-coder model doesn't work so well. UNIX programmers, many of which were not the lone programmers you make them out to be, had a code management system based on the locking philosophy. Fortunately, someone finally stepped back from it and realized that there was a better way to handle code management. This is why CVS was born. That being said, I think CVS should be used in any event 'cause it is the best thing Linux has, currently, and irritating code management is much Much MUCH better than none at all. If you want a code management system based on locking files, use RCS or SCCS. There are also other alternatives that give the other features you are looking for, but at a cost. It is your choice if you wish to remain in the dark ages of code management. Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: revision numbers
That source file seems to have been passed around between several development efforts that use RCS or CVS for version control. Each time the file was Actually, from the log it looks like someone in the same effort renamed it a couple times. each time it was renamed the revision was reset to 1.1. Does this file have a $Log$ marker in it at this point? If not then one of the renames deleted it and this is your problem. Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: incorrect return code on vms...
Larry Jones wrote: I don't think diff-utils is interested in running on non-Unix/Posix systems. CVS is (although it doesn't quite succeed just yet). We use CVS under VMS here and it works fine, with the exception of the release command, but DELETE works just fine as a replacement. Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVSIGNORE won't ignore .conf files
Richard Ponton wrote: I tried using both .cvsignore and the CVSIGNORE environment variable. If you are importing, checkout CVSROOT/cvswrappers first and edit to add: *.[Cc][Oo][Nn][Ff] -k 'kkv' Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: No space left on device error during cvs status/update
You write: Pretty darn sure. I checked and double-checked and triple-checked and then had other smarter people check for me: Filesystemkbytesused avail capacity Mounted on /dev/dsk/c0t0d0s0 962582 830683 3564996%/ assuming /tmp is part of this device, then if your project is larger than 17.8 Megs your probably running out of space on /tmp. swap 1866405488 181152 3%/tmp Does this mean that the swap partition is mounted on /tmp??? Lot's of space. Rex. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS'ing home directory files; CVS in place
Kalle Hoffman [EMAIL PROTECTED] on 08/03/2000 05:03:47 PM To: "Glew, Andy" [EMAIL PROTECTED] cc: [EMAIL PROTECTED](bcc: Rex Jolliff/YM/RWDOE) Subject: Re: CVS'ing home directory files; CVS in place Andy, Same tree no problem, same directory now that would require some thinking. How would you get CVS directory to point to two repositories? I've never done that. Not true. if there is a subdirectory that contains files from a different repository than its parent and a recursive cvs command is executed from the parent, the client will not switch repositories during the command execution. I havent tried this, but I would guess that the best you could hope for is that files in the other repository directory would cause the server to abort an update with an error. I could see how such files would simply be added to the poarent's repository though. Rex.
Re: CVS'ing home directory files; CVS in place
[EMAIL PROTECTED] (Larry Jones) on 08/04/2000 10:24:28 AM [EMAIL PROTECTED] writes: Not true. if there is a subdirectory that contains files from a different repository than its parent and a recursive cvs command is executed from the parent, the client will not switch repositories during the command execution. I havent tried this, [...] Obviously. It works just fine in reasonably recent CVS releases. Admittedly, I based my comment on memory from past discussion on the list. Also, I was referring to different remote repositories in particular (for Andy's information). Is it a fact that a child directory can be from an entirely different remote repository specification (ie username, host and repo dir) than a parent and recursive commands will work? Even if this is the case I would be wary of using this ability. Rex. (who wishes he had autogenerated Calvin and Hobbes quotes. :) )
Re: CVS'ing home directory files; CVS in place
[EMAIL PROTECTED] (Larry Jones) on 08/04/2000 11:33:55 AM wrote: [EMAIL PROTECTED] writes: Even if this is the case I would be wary of using this ability. Why? It has worked from quite some time and there are tests in sanity.sh to verify it. If I cannot recreate the structure easily comewhere else, either for testing or for error recovery, I would shy away from such an approach. It seems to me that building such a structure would involve checkouts from multiple repositories, and I'm lazy enough just to create a copy of the source modules I need in the repository I work out of and import vendor branches into it when I want changes. Rex.
Re: Sorting tags
This theory does not hold if more than one tag is on the latest revision of a file. It also does not indicate the latest tag across all branches. It does not appear that the date of a tag is stored in the ,v file, so it is probably not possible to always determine the latest tag. Rex. Stephen Rasku [EMAIL PROTECTED] on 07/27/2000 09:14:07 AM Please respond to Stephen Rasku [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] cc: (bcc: Rex Jolliff/YM/RWDOE) Subject: Re: Sorting tags From: "Reinstein, Shlomo" [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" [EMAIL PROTECTED] Subject: Sorting tags Date: Thu, 27 Jul 2000 06:14:11 -0700 X-Mailing-List: [EMAIL PROTECTED] archive/latest/19057 Hi, Is there a way of sorting tags according to the revisions that they tag? Specifically I would like to find the latest tag that was put on a given branch. (Suppose that all files in a CVS project are always tagged together, so in general I could take the output of "cvs log" for any single file to see all tags.) The latest tag should be the one with the biggest revision number. So, for the following output: symbolic names: arbitrary-tag: 1.1.4.1 before-purify-fixes: 1.1.4.2 bug-351: 1.1.0.4 ok-to-checkin: 1.1.1.2 rel-2_3: 1.1.0.2 recover-2_4: 1.1.1.2 recover-2_3: 1.1.1.1 stephen: 1.1.1 The latest tag on the bug-351 branch is before-purify-fixes. The bug-351 branch is 1.1.0.4 so all files on this branch will start with 1.1.4. Therefore, the tags arbitrary-tag and before-purify-fixes are both on this branch. Since 1.1.4.2 is greater than 1.1.4.1 it is the later tag. -- Stephen RaskuE-mail: [EMAIL PROTECTED] Senior Software Engineer Web: http://www.tgivan.com/ TGI Technologies http://www.pop-star.net/
Re: Branch/Tag list
cvs history -H -a will at least show all modules that have been tagged. Perhaps that is enough. Rex. "Kuykendall, PR Paul (8807)" [EMAIL PROTECTED] on 07/13/2000 02:01:54 PM To: "'[EMAIL PROTECTED]'" [EMAIL PROTECTED] cc:(bcc: Rex Jolliff/YM/RWDOE) Subject: Branch/Tag list Is there a command that can give a list of all branches/tags in a given repository? I'm trying to write a script that will automatically build a new branch for a software set given a directory by locating the latest branch tag (eg SW_VERSION_1_0) and from there, the script will generate a branch with a given version number passed in as a parameter (eg. 1_1) to generate a new branch SW_VERSION_1_1. I have read the entire Cederqvist manual, deja archives, and web archives, but havn't been able to find the answer I'm looking for. There is other processing to be done (hence not just doing it manually) but 1) there are many repositories, and 2) the requisite overhead and method of version control is embarasing, hence the need for an easy-to-use script. (Making tools for the lowest common denominator is NOT always a good idea.) Thanks for any info on how to pull a listing of all branch names in a repository. Paul Kuykendall - Paul Ryan Kuykendall, Software Engineer [EMAIL PROTECTED]903-457-8807 Raytheon Company -- Aircraft Integration Systems
Re: CVS support for /cvs rm -rf/???
If you're client is running under unix, you can do something like:
find . -prune CVS -type f -exec rm \{} ; cvs remove \{} \;
Rex.
Shawn Anderson [EMAIL PROTECTED] on 07/07/2000 08:59:13 AM
To: CVS ListServe [EMAIL PROTECTED]
cc:(bcc: Rex Jolliff/YM/RWDOE)
Subject: CVS support for /cvs rm -rf/???
BlankAm trying to figure out the best way to transport full directory
hierarchies into the Attic. If I were to do the following::
$: rm -rf modulename [except CVS dirs]
$: cvs -rm -rf modulename
$: cvs ci -m "removed directory" modulename
We would like to do something like this in order to maintain integrity, as
opposed to just logging into the repository and doing an rm -rf from
$CVSROOT.
Thanks in Advance
msa
Title: Blank
Am trying to figure out the best way to transport full
directory hierarchies into the Attic. If I were to do the
following::
$: rm -rf modulename [except CVS
dirs]
$: cvs -rm -rf modulename
$: cvs ci -m "removed directory"
modulename
We would like to do something like this in order to
maintain integrity, as opposed to just logging into the repository and doing an
rm -rf from $CVSROOT.
Thanks in Advance
msa
Compuserve GIF
RE: .trunk patch refinement
Mike Little [EMAIL PROTECTED] on 06/19/2000 09:12:42 AM To: "'[EMAIL PROTECTED]'" [EMAIL PROTECTED], "'[EMAIL PROTECTED]'" [EMAIL PROTECTED] cc:(bcc: Rex Jolliff/YM/RWDOE) Subject: RE: ".trunk" patch refinement -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] [...] OK, so exactly how is this different from "-r1"? Would '-r1' work if some previous cvs admin had updated vast numbers of the trunk revisions to 3.x (presumably when version 3.0 of the product was released)? I would just like to point out that trying to use CVS revision numbers as module or system version numbers is a bad, bad thing to do. This cannot be reiterated enough, and I realize that you did not suggest doing it Mike, but some people might get the mistaken impression that this use of revision numbers is not the mistake that it is. Rex.
RE: loginfo question
Only the first match gets executed, How about: # ^test/dir1* bla "%s" olaf, john ^test* bla "%s" john Rex. Chris Cameron [EMAIL PROTECTED] on 06/08/2000 06:14:35 PM Please respond to "[EMAIL PROTECTED]" [EMAIL PROTECTED] To: 'Olaf Meding' [EMAIL PROTECTED], info-cvs mailing list [EMAIL PROTECTED] cc:(bcc: Rex Jolliff/YM/RWDOE) Subject: RE: loginfo question On Friday, June 09, 2000 9:45 AM, Olaf Meding [SMTP:[EMAIL PROTECTED]] wrote: Can someone explain why CVS does not send an email notification to both john and olaf? In either case, I commited a file in test/dir1 (see below). Is there a way to fix this? I would like one person to get notifications for all sub-directories and the other only for a specific sub-directory. Below are lines from my loginfo file. * case 1 * ^test* bla "%s" john ^test/dir1* bla "%s" olaf # why does olaf not get and email? * case 2 * ^test/dir1* bla "%s" olaf ^test* bla "%s" john # why does john not get an email? The first match is used in all the info files (Cederqvist section C.3). We use a loginfo script to control who gets e-mails (you can add on extra parameters to be passed to your script). *** Chris CameronOpen Telecommunications NZ Ltd Senior Solution Architect [EMAIL PROTECTED] P.O.Box 10-388 +64 4 495 8403 (DDI) The Terrace fax: +64 4 495 8419 Wellington cell: +64 21 650 680New Zealand Life, don't talk to me about life (Marvin - HHGTTG)
Re: Could timestamps be replaced with MD5?
Lenny Foner [EMAIL PROTECTED] on 04/18/2000 08:36:12 AM To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Rex Jolliff/YM/RWDOE) Subject: Could timestamps be replaced with MD5? Of course, it's entirely likely that there are wider-than-32-bit CRC's which are much faster to compute than either MD5 or SHA-1. Such CRC's presumably only require -reading- the entire file, but not storing -all- of it in memory at any given time. MD5 is only required to see each contiguous 512 bytes of a file at a time concurrently. Rex.
Re: status feature
cvs co -c will give a list of module names. But you must define the module in CVSROOT/modules in order for it to show up on this list. Rex. Dave Sherohman [EMAIL PROTECTED] on 04/13/2000 10:01:10 AM Please respond to [EMAIL PROTECTED] To: Michael Gersten [EMAIL PROTECTED] cc: [EMAIL PROTECTED], Mark Harrison [EMAIL PROTECTED], Win32 M$ [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Rex Jolliff/YM/RWDOE) Subject: Re: status feature On Thu, Apr 13, 2000 at 11:42:08AM -0500, Michael Gersten wrote: List of projects: mkdir will-be-big cd will-be-big cvs get . *shudder* I was hoping for a way of just getting all the project _names_, not all their files... (I'm a fledgeling CVS admin at a company that's never used any sort of document control consistently before. We've got a flock of ~40 small programs/projects and I don't want to have to manually maintain a list of them all.) -- The Shortest Windows Manual: "Turn off the power switch." Geek Code 3.1: GCS d- s+: a- C++ UL++$ P L++ E- W--(++) N+ o+ !K w---$ O M- !V PS+ PE Y+ PGP t 5++ X+ R++ tv- b++ DI D G e* h+ r++ y+
Re: About buttons....
Richard Wesley [EMAIL PROTECTED] on 02/18/2000 11:20:16 AM To: [EMAIL PROTECTED] (CVS-II Discussion Mailing List) cc:(bcc: Rex Jolliff/YM/RWDOE) Subject: Re: About buttons [ On Friday, February 18, 2000 at 17:38:32 (CST), Win32 M$ wrote: ] Subject: About buttons There is few more, but I think that will make the point. So, in fact, the tool user would rather setup the options he wants to use, and he can forget about all the troubles with Ver. Cntrl. The different approach is for the tool maker - his job is to make a tool smart enought to do the right things when the button is pressed. We are a tool makers in this forum, and we should have some concern for the "users". We (toolmakers) know the mechanics behind the tool, and we can use it even if it's broken or difficult/complicated. But we should take care to make a life for the "users" easier. Hmm perhaps you should take a long hard look at some other tools, such as Aegis and perhaps some commercial or semi-commercial tools too. My point is that tools users will use the tools in a "smart" way, not the "hard" way. Hard way is in use only in the special/emergency cases. It's a shame that CVS is not integrating via SCC API or COM. There in an attempt to do that thought, but so far it is stuck. You're in the wrong universe. There are no such APIs here. Stuff and nonsense. For starters, .cvsrc allows you to customize the behavior of the cvs commands under *nix so that they have the desired default behavior. This has nothing to do with a 'CVS API'. Beyond that, there are a number of open source graphical front ends to cvs, including WinCVS, jCVS, WebCVS, MacCVS, MacCVS Client and MacCVS Pro. WinCVS, MacCVS Pro and MacCVS have integration of the type described into the CodeWarrior environment under both Windows and Macintosh. These tools are distinct from CVS, just because they communicate with CVS does not mean that CVS provides an API. It does not currently. I wrote the aforementioned MacCVS integration tool and I read this list, so please don't presume to speak for me when you make statements like "There are no such APIs here." There are such APIs here provided by folks who are more interested in promoting cvs than worshipping it. I also know for a fact that Alex Paterneau (WinCVS) and Alberto Barbati (abCVS) read this list. The post you just harshed on even mentions the effort to integrate cvs into MS Developer Studio, which is discussed on this list from time to time. Greg is correct. There is currently no API included in the CVS distribution. There is only the command line client, which can be activated programmatically using the windows API (WinExec). There is also the client-server protocol which is documented. One could write an API, and perhaps convince the maintainers of CVS to include it in the contrib directory. But it is debatable whether anything would be gained by adding an API to the main codeline. If you can't say something useful, just shut up. And if you can't shut up, at least have the decency to only speak for yourself and not the entire community. For the most part greg speaks for me also, as a good portion of what he says I agree with. This last paragraph is not adding anything useful to the discussion, and so violates the very request you make. I sugggest you take your own advice is this regard. Rex.
Re: Enhancement suggestion
I dont think you understood the request. The keyword replacement was desired, but in such a way as to not expand the field. ie: $Author: williams $ can become $Author: rexj$ but $Author: rexj $ would become $Author: will $ Rex. [EMAIL PROTECTED] (Paul Sander) on 02/15/2000 04:34:47 AM To: [EMAIL PROTECTED], [EMAIL PROTECTED] cc:(bcc: Rex Jolliff/YM/RWDOE) Subject: Re: Enhancement suggestion --- Forwarded mail from [EMAIL PROTECTED] Oracle Developper uses propriettary pseudo-binary file format, which is fault prone -- if CVS changes length of keyword value (e. g. $Author: xy $ to $Author: xyz $), Oracle Developper fails to open the file. It is possible to eliminate this disadvantage of CVS - simply change the behaviour of expand_keywords function in rcs.c. But I imagine a new kflag (not compatible to RCS but useful for files that cannot be changed in length by CVS), e. g. -kvp (to express our goal to refuse migration from CVS to PVCS ;-) Checking in and out of file with -kvp flag would: * NOT expand $Keyword$ * expanding $Keyword: Value $ count length of the old Value and cut the new one (if longer than) to the length or right pad it with spaces (if shorter than). Have you looked into the existing -kk and -ko keyword expansions? If they're not in the CVS documentation then you'll find it in the RCS man pages, specifically in co(1). --- End of forwarded message from [EMAIL PROTECTED]
