RE: How to manage oracle custom.pll libraries
Can you explain what you mean by enhancements A, B, and C? If all of these new features: A, B, and C are fairly independent but all modify the same files, then one approach would be to put each feature on its own branch. But if you can make sure that the development for A, B and C does not happen at the same time, and know what order you need to develop them in, you don't *need* branches, do you? Of course you might decide to have branches anyway, because that would allow you to fix bugs on A and develop on B at the same time. * Keep your branches short -- the longer the branch the further away you are from the main branch, which means merging becomes more difficult. * Create a tag each time you do a merge. This could be a life saver if you have to make a second merge from a branch. * Always merge changes back into the main branch, not the other way around. (This is real problem with the separate DEV, TEST, and PROD branches idea. You want to maintain as few of branches as possible). I agree wholeheartedly. I would add: * Before you create a branch, think very carefully. - Know exactly what the branch is for; - Know who's job it will be to merge it back; - Know when it will be merged back; - Allocate time for the merging process (including a system test of the merged code!). In short, don't branch unless you are absolutely certain that you have to branch, and that you are ready for the consequences. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Getting commitinfo changes back to client
Dickson, Craig [mailto:[EMAIL PROTECTED] wrote: I use a script called from my commitinfo file to format all Java files before they get comitted to the repository. This works fine, all Java files in the repository are formatted nicely. Bad idea. The repository should store exactly what it is given, it should not modify anything (the only exception being the well-documented keywords such as $Id$). Your commitinfo script should, instead, simply check the formatting and issue an error code - thereby aborting the commit - if the formatting is wrong. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com/) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
best windows client?
I have CVS setup on a Linux server. I have several Windows clients that are using WinCVS... I have done some searching and nothing else really comes up for Windows Is that the best client to use? Specifically what I am looking for would be a client that would let a user pick individual files from the repository and then be able to check out those files...? Is there anything like that available for CVS? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: concept of web development with cvs
Gene Ballard [mailto:[EMAIL PROTECTED] wrote: Hi, Greetings and salutations! I've read through the cvs documentation but I need help understanding the best way to approach my web project. Current Settings 1. Project - php/mysql shopping system currently running on a Linux test server. 2. CVS is loaded on the Linux webserver that runs the php project. 3. I have created a Repository on the Linux server in /usr/local/cvsroot 4. I have cygwin http://www.cygwin.com/ running CVS on my Win 2k PC. (friend said this was more stable than the windows gui for cvs) Maybe, it may depend on which CVS GUI he's referring to (there are several), but I've found the Windows command-line version of CVS to be quite solid. I'm trying to understand how to setup cvs for my web project so when we update a file, we can instantly test it through the web browser. Do we move the website files into the /usr/local/cvsroot dir and point apache to these files? Or what's the best way to approach web development with cvs? Check out the loginfo script: http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs_18.html#SEC171 in particular the section Keeping a checked out copy. Also, when I Checkout a file from the cygwin command line on my Windows PC, I assume I will navigate to the file using my favorite editor, save my edits then push the file back to the server? I've been trying to connect to cvs on the webserver but it says, No such file or directory. We'll need a little more information to diagnose this, I think. Can you post the exact command sequence you use, and the exact error message? -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com/) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: best windows client?
Specifically what I am looking for would be a client that would let a user pick individual files from the repository and then be able to check out those files...? To view all the hideous detail of a repository without checking it all out, try either: CVSWeb: http://people.freebsd.org/~fenner/cvsweb/ or ViewCVS: http://viewcvs.sourceforge.net/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: best windows client?
Title: RE: best windows client? Hey there, I just CVS on windows for my development in VisualStudio.Net. I like: SmartCVS (Java based, general management client) TortoiseCVS (Explorer shell integration) PushOK Cvs Proxy (VS.Net Integration) Thanks, Steven Behnke -Original Message- From: Phil Labonte [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 09, 2003 6:57 AM To: [EMAIL PROTECTED] Subject: best windows client? I have CVS setup on a Linux server. I have several Windows clients that are using WinCVS... I have done some searching and nothing else really comes up for Windows Is that the best client to use? Specifically what I am looking for would be a client that would let a user pick individual files from the repository and then be able to check out those files...? Is there anything like that available for CVS? ___ 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: best windows client?
I tried to get used to WinCVS. Try TortoiseCVS instead: http://www.tortoisecvs.org/ pc -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Labonte Sent: Tuesday, December 09, 2003 6:57 AM To: [EMAIL PROTECTED] Subject: best windows client? I have CVS setup on a Linux server. I have several Windows clients that are using WinCVS... I have done some searching and nothing else really comes up for Windows Is that the best client to use? Specifically what I am looking for would be a client that would let a user pick individual files from the repository and then be able to check out those files...? Is there anything like that available for CVS? ___ 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
FW: best windows client?
-Original Message- From: Peter Connolly Sent: Tuesday, December 09, 2003 11:24 AM To: 'Rod Macpherson'; Peter Connolly Subject: RE: best windows client? Tried Tortoise but did not like the idea that the whole file system would be exposed to CVS for all the users of CVS at our company. Wanted a more project-oriented approach. There are two strategies that we use to filter the repository for our users: 1) Define modules in the 'modules' file so that they can easily check out portions of the tree that pertain to them 2) Use LockDir and directory permissions to limit who can check in changes to certain, protected portions of the tree. There is also the optional 'readers' and 'writers' admin files that can define who can read or write to the repository. If that isn't enough and more separation is required, then consider splitting up the repository into separate repositories. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Completion messages
I noticed that all of the messages that seem to be returned to the client use the function error(). Is there a function that returns success messages? When reading the code the messages that I normally receive from the server are all using the function error. The only difference is that the errors that are meant to terminate the session pass a 1 in for the first parameter, and everything else passes a 0 for the first parameter. Are all of the messages that pass a 0 in for the first parameter, meant to be the successful messages? Brice Oliver Systems Analyst, Infrastructure Product Development Ontario Systems Tel 765.751.7100 Fax 765.751.7199 mailto:[EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2003 7:02 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Completion messages Brice Oliver writes: The example I have is when running the add command, I get back something like scheduling file FILE . . . Where is the code does it contain the message that get returned to the user that are not error messages? I have looked in add.c and that is where I found the error messages, but I am unable to find the completion messages. Look again -- that's where they are. -Larry Jones I don't want to learn this! It's completely irrelevant to my life! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: best windows client?
On Tue, Dec 09, 2003 at 09:56:31AM -0500, Phil Labonte wrote: I have CVS setup on a Linux server. I have several Windows clients that are using WinCVS... I have done some searching and nothing else really comes up for Windows Is that the best client to use? Specifically what I am looking for would be a client that would let a user pick individual files from the repository and then be able to check out those files...? Is there anything like that available for CVS? The eclipse IDE lets users select individual files. You really have to stay on top of updates, though, because it implements the CVS protocol internally in order to accomplish this, and minor updates have been known to break it. My favorite win32 client (and the only one I actively support for our users) is TortoiseCVS. http://tortoisecvs.sourceforge.net/ It's based on cvsnt and integrates nicely with the shell. It handles all the normal developer tasks quite nicely. For administrative tasks, you may still want the command line tools. Regards, Geoff ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Visual Studio .NET with CVS
I have been looking into using CVS from within Visual Studio .NET in Windows. So far I have only found Igloo, but it doesn't seem to work (undefined errors, locks up) and there hasn't been any development on the website since 11th April 2002. Is there a newer version anywhere? Is there anything else I can use. I have also seen several people recommend TortoiseCVS, which we are using at the moment. It's not too bad, but I've had at least one bad crash (wiped three modules from my hard disk, including uncommitted files) and several odd errors. I've been looking at CVS Shell Extension from WoLoSoft (http://www.wolosoft.com/en/cvs-ext/index.html). Has anyone used this? Is it possible to install it alongside TortoiseCVS? Thanks for any help. Tom Isaacson mailto:[EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Best Windows Client??
I have CVS setup on a Linux server. I have several Windows clients that are using WinCVS... I have done some searching and nothing else really comes up for Windows Is that the best client to use? Specifically what I am looking for would be a client that would let a user pick individual files from the repository and then be able to check out those files...? Is there anything like that available for CVS? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: best windows client?
We are using LinCVS, which runs perfectly on Windows, Linux (and also MacOSX, though I have not tried that). Maarten ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Format for 1.11.10's contrib's loginfo, used by log_accum commit script?
I asked this question before and got pointed to the Cederqvist manual, which does *not* help at all. Please don't tell me to RTFM, the answer is not there. We are on CVS 1.11.5, moving to 1.11.10. We are using a really old version (1.11.1p) of the log_accum.pl and loginfo files. I would like to upgrade to the commit_prep and log_accum scripts that are included in the $CVS/share/cvs/contrib directories of 1.11.10. However, I can't find any documentation or examples of what this variant of the 'loginfo' file should look like. When I run with the old formatted version of the loginfo file, I get a Too many arguments error coming out of process_argv. Now, I could spend a week learning PERL and figure out the format that is required... BUT, I'd really rather not. Does anyone out there know the file format required for the 'loginfo' file that is included in the 'contrib' directory of 1.11.10 CVS??? Presumably someone out there wrote this thing and knows what inputs it takes??? Thanks, pc Peter Connolly, CNET Networks, Inc. (415) 344-2840 [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS Feature Version 1.12.4 Released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 CVS feature version 1.12.4 has been released. Feature releases contain new features as well as all the bug fixes from the stable release. This release adds promotable read locking code which prevents CVS from locking more than a directory at a time for write access. This can help prevent large commits from interfering with other CVS processes which only want read access. Largefile support has also been added for Solaris and other systems which support large files. We recommend this upgrade for all CVS clients and servers already running the feature release and those users who like to stay on the cutting edge! Take a look at the NEWS file http://ccvs.cvshome.org/source/browse/ccvs/NEWS?rev=1.171content-type=text/x-cvsweb-markup from the source distribution or go directly to the downloads page http://ccvs.cvshome.org/servlets/ProjectDownloadList. MD5 sum: a4926e262c8e8ae5501c61c2098cbc16 cvs-1.12.4.tar.bz2 Derek Price Public key available from http://pgp.mit.edu. - -- *8^) Email: [EMAIL PROTECTED] Get CVS support at http://ximbiot.com! - -- I will not say Springfield just to get applause. I will not say Springfield just to get applause. I will not say Springfield just to get applause... - Bart Simpson on chalkboard, _The Simpsons_ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org iD8DBQE/1keRLD1OTBfyMaQRAgEqAKCmCPHxWOwg/++cHeZ3zG1MmtmVvwCg1MFB uM3Kt+vHQ5wacxgHfY9k8T4= =Y3El -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: best windows client?
On Tuesday 09 December 2003 09:56 am, Phil Labonte wrote: I have CVS setup on a Linux server. I have several Windows clients that are using WinCVS... I have done some searching and nothing else really comes up for Windows Is that the best client to use? Specifically what I am looking for would be a client that would let a user pick individual files from the repository and then be able to check out those files...? Is there anything like that available for CVS? I use Visual Slickedit (both Windows and Linux). It is a commercial IDE: http://www.slickedit.com ___ 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: Format for 1.11.10's contrib's loginfo, used by log_accum commit
Peter Connolly writes:
Now, I could spend a week learning PERL and figure out the format that
is required...
BUT, I'd really rather not.
Perl isn't that hard to read.
Does anyone out there know the file format required for the 'loginfo'
file that is included in the 'contrib' directory of 1.11.10 CVS???
I believe you want something like:
commitinfo:
DEFAULT commit_prep -u ${USER}
loginfo:
DEFAULT log_accum -u ${USER} %s
-Larry Jones
Who, ME? Who?! Me?? WHO... Me?! Who, me??? -- Calvin
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Completion messages
Brice Oliver writes: Are all of the messages that pass a 0 in for the first parameter, meant to be the successful messages? No, but some of them are. Some of them are also warnings. Which are which should be obvious from the message text. -Larry Jones In my opinion, we don't devote nearly enough scientific research to finding a cure for jerks. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: sticky non-branch tags are sometines treated as branches in empty
On Wed, 3 Dec 2003, Larry Jones wrote: However, we have found out that sometimes commit on these sticky tags succeed, because CVS somewhere in the process _converts_ the sticky normal tag into a branch! This happens when there are empty directories in the tree on which cvs update -r TAG has been done. The problem is that tags do not have an independent existance -- they only exist inside RCS files. Thus, a tag can be a branch tag in one file and a non-branch tag in another. The rule CVS uses is that if the tag is a non-branch tag in any file in the directory, then the tag is marked as a non-branch tag in the CVS/Tag file; otherwise, it is marked as a branch tag, which naturally results in a branch tag in an empty directory. Just one more reason why you should always use -P on checkout and update and not try to store empty directories in CVS. Unfortunately the problem seems a bit deeper than that: the above rule doesn't seem to make any sense for parent directories (which by nature aren't empty), even if there are files there that contain the non-branch tag, as long as nothing is checked out on them. For example, starting on an empty directory: mkdir repo cd repo cvs -d WHATEVER co -r MYTAG parent/anotherparent/subdir In this case cvs has to create parent and then parent/anotherparent before checking out the subdirectory we are really interested in. Not only parent and parent/anotherparent have a CVS/Tag file (IMO they shouldn't at all), but their tag is marked as branch (which, again, is wrong). The problem keeps happening every time you check out a tagged subdirectory, i.e.: cvs -d WHATEVER co -r SOMEOTHERTAG parent/subdir2 will put a fake branch SOMEOTHERTAG on parent/CVS/Tag. So if you are not careful you end up generating random branches all over the place every time you try to add new files or directories. My question is, because I invoke the above commands from a wrapper, is it a valid and safe workaround to manually remove CVS/Tag files from the parent directories after running the checkouts? Regards, -- Álvaro Martínez Echevarríaalvarom NO_SPAM_NONONO cisco.com Cisco Systems SJC24/3/A5-3 510 McCarthy Blvd. Milpitas, CA 95035 Phone: +1-408-526-7179 ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Format for 1.11.10's contrib's loginfo, used by log_accum com mit
Perl isn't that hard to read.
Larry, Larry, Larry,... Trust me. If you've never encountered constructs like @_, my,
local($wd, @files); scalars, arrays... (and btw, 'local' is not local, 'my' is
local...how cute), reading it is doable but tediously slow. I'm reminded of a
friend's admonition in college. He said: Physics is easy, once you know it.
I believe you want something like:
commitinfo:
DEFAULT commit_prep -u ${USER}
loginfo:
DEFAULT log_accum -u ${USER} %s
I've tried that and when I commit, I get the following messages:
Processing log script arguments...
Mailing the commit message to (from [EMAIL PROTECTED])
No recipient addresses found in header
which I guess means that $mail_to and its progenitor $addr_list in the
mail_notification subroutine are not being set properlybut no hints as to how to
format those email addresses into loginfo...
General question: Is it really expected that EVERYONE that wants to set up and use
these contrib scripts have to read them, understand them and retro-engineer the inputs?
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Format for 1.11.10's contrib's loginfo, used by log_accum com
Peter Connolly writes: I've tried that and when I commit, I get the following messages: Processing log script arguments... Mailing the commit message to (from [EMAIL PROTECTED]) No recipient addresses found in header which I guess means that $mail_to and its progenitor $addr_list in the mail_notification subroutine are not being set properlybut no hints as to how to format those email addresses into loginfo... General question: Is it really expected that EVERYONE that wants to set up and use these contrib scripts have to read them, understand them and retro-engineer the inputs? Apparently so. It appears that you're expected to customize the log_accum script for your environment. In particular, look for the mlist_map subroutine, both the definition of which and the call are commented out. It appears that you need to set $mlist to the list of recipients somehow -- the commented out code provides one example but you can do it any way you like. The downside of that, of course, is that you *have* to do it, whether you want to or not. -Larry Jones Hey! What's the matter? Can't you take a joke?! It was a JOKE! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS Feature Version 1.12.4 Released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Derek Robert Price wrote: CVS feature version 1.12.4 has been released. Feature releases contain new features as well as all the bug fixes from the stable release. This release adds promotable read locking code which prevents CVS from locking more than a directory at a time for write access. This can help prevent large commits from interfering with other CVS processes which only want read access. Largefile support has also been added for Solaris and other systems which support large files. We recommend this upgrade for all CVS clients and servers already running the feature release and those users who like to stay on the cutting edge! Take a look at the NEWS file http://ccvs.cvshome.org/source/browse/ccvs/NEWS?rev=1.171content-type=text/x-cvsweb-markup from the source distribution or go directly to the downloads page http://ccvs.cvshome.org/servlets/ProjectDownloadList. MD5 sum: a4926e262c8e8ae5501c61c2098cbc16 cvs-1.12.4.tar.bz2 Derek Price Public key available from http://pgp.mit.edu. A note from Mark D. Baushke: HP/UX users may need to use - --disable-largefile, but largefile support should work on other platforms. If anyone can figure out why src/sanity.sh tests are failing on HP/UX with largefiles enabled, we would appreciate the report on [EMAIL PROTECTED]. Regards, Derek - -- *8^) Email: [EMAIL PROTECTED] Get CVS support at http://ximbiot.com! - -- I will not skateboard in the halls. I will not skateboard in the halls. I will not skateboard in the halls... - Bart Simpson on chalkboard, _The Simpsons_ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org iD8DBQE/1ns3LD1OTBfyMaQRApHwAJ9Gh3vDGhLNYsatAKN8Mt3jT+mMLwCfUGNa VJ5CykXREwc3NATMrtwXyUg= =+MDA -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: sticky non-branch tags are sometines treated as branches in empty
On Tue, Dec 09, 2003 at 04:06:49PM -0800, Alvaro Martinez Echevarria wrote: cvs -d WHATEVER co -r MYTAG parent/anotherparent/subdir [...] My question is, because I invoke the above commands from a wrapper, is it a valid and safe workaround to manually remove CVS/Tag files from [parent and parent/anotherparent] after running the checkouts? If you do that, then instead of generating random branches all over the place every time you try to add new files or directories, you'll simply generate random trunk revisions. Probably not what you want. Instead, rewrite those directories' CVS/Tag files to contain revision tags. That way, if a user tries to commit something in parent/anotherparent, they'll get a nasty error message. It's ugly, but at least it fails safe. The user can cvs update -l -rbranch to put the directory on the branch they really want it on, and try again. I'd be tempted to rewrite the revision tag itself, not just the what-kind-of-tag-am-i flag, to something obviously bogus like this_is_a_phony_tag-ask_a_guru_for_help. That way, a user who's seen this before will recognize the bogus tag name and know what the situation is. For users who are new to it, they won't know what's going on, but again it'll fail safe, this time on the human scale: the user will *know* he doesn't know what's going on, whereas a legitimate tag name in the error message might have fooled him into thinking he did know :-) -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: sticky non-branch tags are sometines treated as branches in
On Tue, 9 Dec 2003, Larry Jones wrote: Alvaro Martinez Echevarria writes: In this case cvs has to create parent and then parent/anotherparent before checking out the subdirectory we are really interested in. Not only parent and parent/anotherparent have a CVS/Tag file (IMO they shouldn't at all), but their tag is marked as branch (which, again, is wrong). There is no right answer in this case. CVS simply does not have sufficient information to tag parent directories correctly, whatever that means. (Note that CVS works on a directory at a time; there is no mechanism for files contained in a subdirectory to affect the processing of the parent directory.) If parent directories weren't tagged at all, then new files would be added to the tip of the trunk, which might be better in your situation, but would undoubtedly be much worse in other, equally common situations. Hmmm, I see. It all depends on how you use you repository, I guess. If you're doing something like: CVSROOT/gnu/bash CVSROOT/gnu/libc CVSROOT/linux/kernel CVSROOT/linux/modules where each of those second level subdirectories are (non-branching-)tagged independently from the others, you're in trouble. When you create a new directory CVSROOT/gnu/grep, the last thing you want is that to go under branch 2-05a because such happened to be the last version of bash you checked out. Because this behaviour is clearly wrong in this situation, but the alternative (do not create Tag files in parent directories) would also be clearly wrong in other circumstances, would it be crazy to add a command line option to checkout/update to control which way it goes? Just checking, it doesn't hurt to ask... :) Regards, -- Álvaro Martínez Echevarríaalvarom NO_SPAM_NONONO cisco.com Cisco Systems SJC24/3/A5-3 510 McCarthy Blvd. Milpitas, CA 95035 Phone: +1-408-526-7179 ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
