win version?
Hi Is there win version of gnu cvs? thx for answer sj ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: win version?
Hi there... If u mean a windows version of GNU CVS (which runs on Linux), then try http://www.cvsnt.com/cvspro/ Regards Sandhya. Hi Is there win version of gnu cvs? thx for answer sj ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
(no subject)
What is the $HOME used for on the server? I've been successfully using CVS for 3 years, and I love it! Now, whe are getting more users (upto 100). Currently, each user has it's normal account on the server. However, to free up some space and redundant administration, I would like to set the users home dir to be a common dir on the server and not have a seperate user home dir for each user. Will this work? What is the $HOME used for? /G --- www.gunnarahlberg.com --- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Is import really necessary?
IIRC, I saw a gnu.cvs.help post several months ago that showed how
to initiate a project without using import, and that this approach
struck me then as more logical/reasonable somehow.
But now I can't find this post via Google Groups. Maybe I dreamt
it? If not, or if anyone knows what this import-less alternative
may be, please refresh my memory.
TIA,
jill
--
To se^n]d me m~a}i]l r%e*m?o\v[e bit from my a|d)d:r{e:s]s.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is import really necessary?
Hello Jill, * On Mon, Dec 20, 2004 at 01:10:30PM + J Krugman wrote: But now I can't find this post via Google Groups. Maybe I dreamt it? If not, or if anyone knows what this import-less alternative may be, please refresh my memory. You might refer to that one: http://lists.gnu.org/archive/html/info-cvs/2004-03/msg00246.html (the link I posted in a follow-up is not working, please contact me off-list if you want to get that script). HTH, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://www.viceteam.org/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: win version?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 SJ wrote: Hi Is there win version of gnu cvs? thx for answer sj If you only need the Windows CVS client, the cvshome.org version of CVS should work fine and, judging by some recent postings to this list, sometimes even better than CVSNT. Binaries are posted here: https://ccvs.cvshome.org/servlets/ProjectDocumentList?folderID=83expandFolder=83folderID=80. Cheers, Derek - -- *8^) Email: [EMAIL PROTECTED] Get CVS support at http://ximbiot.com! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBxuVfLD1OTBfyMaQRAv+rAKCOaTgW7U2Pq39hzyFejiv1HDLRnACg3uiB phremYnMKX5ykIllnp4Kod4= =hrsy -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
CVS Server $HOME (was Re: (no subject))
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gunnar Ahlberg wrote: What is the $HOME used for on the server? I've been successfully using CVS for 3 years, and I love it! Now, whe are getting more users (upto 100). Currently, each user has it's normal account on the server. However, to free up some space and redundant administration, I would like to set the users home dir to be a common dir on the server and not have a seperate user home dir for each user. Will this work? What is the $HOME used for? /G --- www.gunnarahlberg.com --- Assuming you've set up :ext:/SSH access to your CVS server and private/public keys are available as an access method, the SSH keys are probably stored in $HOME/.ssh. Other than that, $HOME shouldn't be used for much on the server, provided that the only command that ever gets executed there is `cvs server'. In that case, it should be safe to share the home dir as you described if you can keep the shared authorized_keys file updated as needed. If you are using the :pserver: access method, $HOME should not be used at all on the server end. Cheers, Derek - -- *8^) Email: [EMAIL PROTECTED] Get CVS support at http://ximbiot.com! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBxua/LD1OTBfyMaQRAui9AJ404DiYSpVK4067VgRDN5yARFXkFwCg0mNy u0VLVwbsZp7H5IJ6A6ANPR0= =/tEc -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cvs export: (no files)
[EMAIL PROTECTED] wrote: Hi all I think the situation is There are two module modA modB if I tag modA with 'tag123' then I export modB with 'tag123', it will return the directories of modB but not the files Is this a bug? Jacinle Hint, You are seeing the effects that are described as desired in the linked messages. :) http://lists.gnu.org/archive/html/info-cvs/2004-03/msg00394.html http://lists.gnu.org/archive/html/info-cvs/2003-03/msg00250.html If you checkout/export with a tag, cvs only checks out what you told it to, i.e., files with that tag. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Updating revision number on a branch.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Heather wrote: Heh, I think you misunderstood my second message. I meant that we wanted to make the change for cosmetic reasons, not that it WAS a cosmetic change. After reading on how the branches are created, I understand why you don't want to mess with those. However, I don't understand what the problem is with updating the revision numbers on the main trunk. Am I seriously missing something because I see people doing this all the time? :) Or are all these people just treading into dangerous waters? And yes, we know how to use symbolic tags and have been using them, so the issue isn't that we don't know how to do that. This is just a curiosity thing at this point in time. The basic problem is that you will may very well find out that CVS is making assumptions about revision numbers fitting some 1.x format, as revision numbers starting with anything other than `1.' are not tested thoroughly in the regression test suite despite their being some legacy support since, at least in theory, and RCS repository should be importable into CVS. Treading dangerous waters means that you may also very well find out that most of CVS's functionality will still work correctly, but you might encounter occasional bugs that, due to lack of interest from others, you will likely be stuck fixing. Patch submissions of fixes for standard functionality that breaks when !1.x revisions are encountered would likely be accepted by the CVS developers if they don't break any other functionality, but you might also encounter some edge cases like Alan Dayley pointed out from CVSNT where new revisions are added with 1.x revisions again despite others at 2.x or otherwise, and the CVS developers might have little interest in a fix for such an issue, though I can imagine some simple patches for such an issue that might be accepted. Anyhow, if you have the resources to deal with these issues and work with the CVS developers on patch submissions, by no means should you let me discourage you and by no means would I want to discourage you. I'm just trying to provide you with fair warning of what you might encounter if you tried this. Cheers, Derek - -- *8^) Email: [EMAIL PROTECTED] Get CVS support at http://ximbiot.com! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBxu4ILD1OTBfyMaQRAhKeAKDsuZnOVNZQdYtxYK8Bpc5ghDF4ZACg1fuY sn3tu4kreanB+POZJwuW2Mo= =E4tS -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is import really necessary?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Spiro Trikaliotis wrote:
Hello Jill,
* On Mon, Dec 20, 2004 at 01:10:30PM + J Krugman wrote:
But now I can't find this post via Google Groups. Maybe I dreamt
it? If not, or if anyone knows what this import-less alternative
may be, please refresh my memory.
You might refer to that one:
http://lists.gnu.org/archive/html/info-cvs/2004-03/msg00246.html
(the link I posted in a follow-up is not working, please contact me
off-list if you want to get that script).
Assuming all you need to do is create a new project in CVS based on an
existing tree at /home/user/newtree, the following should work:
cvs co -ldtop .
cd top
mv /home/user/newtree .
find newtree -exec cvs add {} \;
cvs ci
Cheers,
Derek
- --
*8^)
Email: [EMAIL PROTECTED]
Get CVS support at http://ximbiot.com!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBxugPLD1OTBfyMaQRAnHAAJ9CM5kL7mDQdW0lQDiNrFvv1lZzXgCeJnbV
AlKb39hP7bbi5fYX/40l3pw=
=U9eE
-END PGP SIGNATURE-
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Update and removing non-versioned workspace files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark D. Baushke wrote: Keith Chong [EMAIL PROTECTED] writes: Is there a way to use update and have any non-versioned files deleted from your local workspace? -C doesn't appear to do it. I have been known to use the script below when I was still playing with .cvsignore and Makefile files and needed to have a pristine copy of the files that were cvs controlled in my directory... it was a quick and dirty hack. When working with a project that doesn't have a Makefile setup such that `make distclean' does the trick, I usually just check out a fresh copy of the sources when I need a pristine copy. i.e. 'cd ..; rm -rf project; cvs co project'. Of course, that can be annoying given a low-bandwidth connection to your CVS server. Cheers, Derek - -- *8^) Email: [EMAIL PROTECTED] Get CVS support at http://ximbiot.com! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBxu88LD1OTBfyMaQRAghVAKCPfLw8Tw/1VoY3eVY1U2MNrKo67QCguejf uVgzJD0Wp+BwkWffOByPZHo= =LCyD -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Importing old repository remotely to new server?
Hello, I am not new to CVS, but am completely new to setting up a new non-pserver repository. Right now we have a repository that is located on a university linux server (version 1.0.6?), and we have no access to the repository except via CVS. What we would like to do is duplicate the existing repository on a new Linux box running a newer version of CVS. Is there an easy way to have a client machine connect to the old server, query all of the information about versions, files, branches, etc. and then somehow automatically transmit that information to the new CVS server? Since we can see most of this information doing simple command line queries, so it should, in theory, be possible. Right now we are planning to just import the current version of the source into the new server, but I hate to lose all of that history if we dont have to. Thank you, James Day ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Importing old repository remotely to new server?
Hello, I am not new to CVS, but am completely new to setting up a new non-pserver repository. Right now we have a repository that is located on a university linux server (version 1.0.6?), and we have no access to the repository except via CVS. What we would like to do is duplicate the existing repository on a new Linux box running a newer version of CVS. Is there an easy way to have a client machine connect to the old server, query all of the information about versions, files, branches, etc. and then somehow automatically transmit that information to the new CVS server? Since we can see most of this information doing simple command line queries, so it should, in theory, be possible. Right now we are planning to just import the current version of the source into the new server, but I hate to lose all of that history if we dont have to. Thank you, James Day ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Importing old repository remotely to new server?
James Day writes: Is there an easy way to have a client machine connect to the old server, query all of the information about versions, files, branches, etc. and then somehow automatically transmit that information to the new CVS server? Since we can see most of this information doing simple command line queries, so it should, in theory, be possible. Indeed, and I've suggested it in the past as a good project for someone to get familiar with the client/server protocol. Alas, no one has taken me up on it. Your best bet is to ask the administrator of the current repository whether they support any remote access tools like CVSup or rsync. If not, ask if they'll tar up your portion of the repository for you. -Larry Jones The game's called on account of sudden death. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Root of hierachy
Hi all CVS specialists, I´m a beginner at CVS, so forgive me if I'm asking nonsense. I've imported a module PI.0 into CVS. Import has created a working branch as avendor and a revision on it as arelease. The arelease files are all 1.1.1.1. I've now checked out my working directory as avendor, my working branch. I've now changed one file (say one t.c) from 1.1.1.1 to 1.1.1.2 and committed that to the working branch avendor. The I've tagged this new revision to brelease. My problem now is, how to convert this new release brelease to the Root-Branch (that is something 1.*)! What is the name of the Root-Branch? I've never been asked to create one. And the graphical display doesn't show a name corresponding to revision 1.1. The essential question is: HOW COULD I CREATE A NAME FOR THE ROOT BRANCH??? What I want to see is revisions 1.1 of all files for the Root and a revision 1.2 for the file t.c, when I'm working Root, whatever that is... Thanks very much for yor help, Fritz Bode ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Root of hierachy
ngc891 writes: I've now checked out my working directory as avendor, my working branch. NO! The vendor branch is *only* for vendor releases. For local changes, you want to be working on the trunk, not the vendor branch. The trunk (what you call the root branch) is what you get when you don't specify any particular revision to checkout. You can switch your existing working directory to the trunk with update -A. I've now changed one file (say one t.c) from 1.1.1.1 to 1.1.1.2 and committed that to the working branch avendor. The I've tagged this new revision to brelease. Unless you're simulating a second vendor release without doing an import, that's completely wrong. My problem now is, how to convert this new release brelease to the Root-Branch (that is something 1.*)! In this particular case you don't have to do anything, but in general, in a working directory on the trunk, do update -jarelease -jbrelease. A normal import would have suggested that. What is the name of the Root-Branch? I've never been asked to create one. And the graphical display doesn't show a name corresponding to revision 1.1. There isn't one. And you can't really create one, either. As I said before, it's what you get when you don't specify any name. What I want to see is revisions 1.1 of all files for the Root and a revision 1.2 for the file t.c, when I'm working Root, whatever that is... That isn't how CVS works. You'll only see 1.x for locally modified files. All the unmodified files will be referenced from the vendor branch and thus be 1.1.1.x. The revision numbers are really for CVS's intenal use, you shouldn't worry about what they are. You should use tags for infomation that's meaningful to you. -Larry Jones It's either spectacular, unbelievable success, or crushing, hopeless defeat! There is no middle ground! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cvs export: (no files)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Hi all I think the situation is There are two module modA modB if I tag modA with 'tag123' then I export modB with 'tag123', it will return the directories of modB but not the files Is this a bug? It's not the optimal behavior perhaps, but it would be somewhat invasive to fix. I would consider a solid and succinct patch submission which implements the behavior you describe, but it would probably be some time before I got around to implementing it myself. Cheers, Derek - -- *8^) Email: [EMAIL PROTECTED] Get CVS support at http://ximbiot.com! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBxz5zLD1OTBfyMaQRAlAUAKCoDKpBvkVTmRiOYFOOs+j+mxBoDgCgkLPw 79URp42n9X2cOmh4livMJF0= =SCtZ -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cvs export: (no files)
Derek Robert Price wrote: [EMAIL PROTECTED] wrote: Hi all I think the situation is There are two module modA modB if I tag modA with 'tag123' then I export modB with 'tag123', it will return the directories of modB but not the files Is this a bug? It's not the optimal behavior perhaps, but it would be somewhat invasive to fix. I would consider a solid and succinct patch submission which implements the behavior you describe, but it would probably be some time before I got around to implementing it myself. Cheers, Derek Derek, which behavior are you suggesting should be implemented? A) when checkout/export is called with a tag, if a File does not have that tag just get the latest version. B) when checkout/export is called with a tag, if no File in the directory has that tag, do not create the directory in the sandbox/export. Here is what I envision (from the description above) jacinleyoung did : cvs checkout modA cd modA cvs tag tag123 cd .. cvs export -r tag123 modB #results in empty directories created in modB, which is the current EXPECTED result. In which case I could support (someone else's patch) to do (B), however (A) is a non starter. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS Server $HOME (was Re: (no subject))
Thank you Derek! I am using SSH as the only connection method. is the .ssh file per session? and what's in it? A copy of the public key? If $HOME is used for the .ssh file, wouldn't two simultaneous users be able to overwrite each others session if they shared the same $HOME? It seems like huge projects with many committers such as the Eclipse or Mozilla projects would have a separate HOME dir per user to prevent the above scenario. Any more thoughts on that? Cheers, /G 2004-12-20 at 15.50 Derek Robert Price wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gunnar Ahlberg wrote: What is the $HOME used for on the server? I've been successfully using CVS for 3 years, and I love it! Now, whe are getting more users (upto 100). Currently, each user has it's normal account on the server. However, to free up some space and redundant administration, I would like to set the users home dir to be a common dir on the server and not have a seperate user home dir for each user. Will this work? What is the $HOME used for? /G --- www.gunnarahlberg.com --- Assuming you've set up :ext:/SSH access to your CVS server and private/public keys are available as an access method, the SSH keys are probably stored in $HOME/.ssh. Other than that, $HOME shouldn't be used for much on the server, provided that the only command that ever gets executed there is `cvs server'. In that case, it should be safe to share the home dir as you described if you can keep the shared authorized_keys file updated as needed. If you are using the :pserver: access method, $HOME should not be used at all on the server end. Cheers, Derek - -- *8^) Email: [EMAIL PROTECTED] Get CVS support at http://ximbiot.com! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBxua/LD1OTBfyMaQRAui9AJ404DiYSpVK4067VgRDN5yARFXkFwCg0mNy u0VLVwbsZp7H5IJ6A6ANPR0= =/tEc -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Root of hierachy
Hi Larry, I think that I've not really understood what CVS means. My understanding is, that when I'm importing a new project, it should be something like 1.0 with a tag like Import. Then I'm creating a branch to work on (say 1.0.1.0). If I'm finished on that branch, I'd put a release tag on it (say brelease). After I've released that version, I'd like to convert this release to the Root revisions (that's like 1.1 or 1.2) by merging and release this Root revision. As you said, this it not how CVS works. Please tell me, how does CVS works. I didn't found it anywhere in the internet (I was looking for it for 3 month :-) ) Should 1.1.1.1 be the Root and 1.1.1.1.1.1 be the first WorkBranch? Could be so, but the release numbers would be hard to remember. I'd really like a way to merge all back to what I'm calling the Root, that is somethink like revision 1.2 or 1.3. As I told before, I'm just a beginner. So, don't push too hard. I'm just trying to understand the background of CVS. --Best Wishes --ngc891 Larry Jones wrote: ngc891 writes: I've now checked out my working directory as avendor, my working branch. NO! The vendor branch is *only* for vendor releases. For local changes, you want to be working on the trunk, not the vendor branch. The trunk (what you call the root branch) is what you get when you don't specify any particular revision to checkout. You can switch your existing working directory to the trunk with update -A. I've now changed one file (say one t.c) from 1.1.1.1 to 1.1.1.2 and committed that to the working branch avendor. The I've tagged this new revision to brelease. Unless you're simulating a second vendor release without doing an import, that's completely wrong. My problem now is, how to convert this new release brelease to the Root-Branch (that is something 1.*)! In this particular case you don't have to do anything, but in general, in a working directory on the trunk, do update -jarelease -jbrelease. A normal import would have suggested that. What is the name of the Root-Branch? I've never been asked to create one. And the graphical display doesn't show a name corresponding to revision 1.1. There isn't one. And you can't really create one, either. As I said before, it's what you get when you don't specify any name. What I want to see is revisions 1.1 of all files for the Root and a revision 1.2 for the file t.c, when I'm working Root, whatever that is... That isn't how CVS works. You'll only see 1.x for locally modified files. All the unmodified files will be referenced from the vendor branch and thus be 1.1.1.x. The revision numbers are really for CVS's intenal use, you shouldn't worry about what they are. You should use tags for infomation that's meaningful to you. -Larry Jones It's either spectacular, unbelievable success, or crushing, hopeless defeat! There is no middle ground! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
CVS/CVSNT Hangs When Checking Out Files
Hello: Having problem checking out all files that are in a CVS repository, some files are checked out and then the checkout process appears to hang: Server Repository on Linux (RedHat 9.0) running standard CVS Repository in /cvsroot Module name in cvsroot: testCVS-SW There are 5 files checked into testCVS-SW: file1.cpp, file2.cpp ...file5.cpp Client Windows XP Professional CVSNT version 2.0.58d Run following command at client: cvs checkout testCVS-SW The directory testCVS-SW is created and file1.cpp, file2.cpp and file3.cpp are checked out but cvs appears to be hung after file3.cpp is checked out. I break out of the program and run cvs again with the same command and then the remaining files are checked out. I can delete testCVS-SW and run the sequence again and the same thing happens almost 100% of the time. On a very rare occasion all 5 files will get checked out at one time. Thanks, Andy ... ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is import really necessary?
In [EMAIL PROTECTED] Derek Robert Price [EMAIL PROTECTED] writes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Spiro Trikaliotis wrote:
Hello Jill,
* On Mon, Dec 20, 2004 at 01:10:30PM + J Krugman wrote:
But now I can't find this post via Google Groups. Maybe I dreamt
it? If not, or if anyone knows what this import-less alternative
may be, please refresh my memory.
You might refer to that one:
http://lists.gnu.org/archive/html/info-cvs/2004-03/msg00246.html
(the link I posted in a follow-up is not working, please contact me
off-list if you want to get that script).
Assuming all you need to do is create a new project in CVS based on an
existing tree at /home/user/newtree, the following should work:
cvs co -ldtop .
cd top
mv /home/user/newtree .
find newtree -exec cvs add {} \;
cvs ci
Yes, that's very much like what I vaguely recall from that post
months ago. How do the end-results differ from doing the ol'
cd /home/user/newtree
cvs import newtree random1 random2
?
To me the import-less approach looks infinitely more logical and
reasonable (for one thing there's no need to come up with phony
vendor and release tags), but the approach via import is so entrenched
I have to assume it has some non-obvious benefits (beyond the fact
that it can be done with just one cvs command), even for cases in
which the vendor tag is not meaningful (e.g. when the project is
one's own shell dot files or versions of the LaTeX file for a paper
one is writing).
While I'm on the subject, I should add that there's a lot about
CVS that just makes no sense to me (this business with import and
the vendor/release tags being one example); I think I'd be a much
happier (and more productive) user of CVS if I only *understood*
the method to the madness, instead of just executing commands by
rote.
I realize that maybe there is *no* method to the madness: CVS is
crazy-looking for historical reasons having to do with its RCS
origins. So maybe I just have to grin and bear it...
jill
--
To se^n]d me m~a}i]l r%e*m?o\v[e bit from my a|d)d:r{e:s]s.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
Re: (no subject)
Hi. set o home user for directory common,as example /home/public, and on create user define home user commom: useradd -g user -s /bin/bash -d /home/public USER Citando Gunnar Ahlberg [EMAIL PROTECTED]: What is the $HOME used for on the server? I've been successfully using CVS for 3 years, and I love it! Now, whe are getting more users (upto 100). Currently, each user has it's normal account on the server. However, to free up some space and redundant administration, I would like to set the users home dir to be a common dir on the server and not have a seperate user home dir for each user. Will this work? What is the $HOME used for? /G --- www.gunnarahlberg.com --- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs atenciosamente Luiz Guilherme Roncati DIS - Departamento de Informatica em Saude UNIFESP - Universidade Federal do Estado de Sao Paulo Fone: (11)5575-4533 ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS/CVSNT Hangs When Checking Out Files
Andy Shepard writes: This is a multi-part message in MIME format. Please do not send MIME and/or HTML encrypted messages to the list. Plain text only, PLEASE! Having problem checking out all files that are in a CVS repository, some files are checked out and then the checkout process appears to hang: What connection method are you using? There are known bugs in some versions of SSH that cause that problem. -Larry Jones Some people just don't have inquisitive minds. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Is import really necessary?
In [EMAIL PROTECTED] Derek Robert Price [EMAIL PROTECTED] writes:
Assuming all you need to do is create a new project in CVS based on an
existing tree at /home/user/newtree, the following should work:
cvs co -ldtop .
cd top
mv /home/user/newtree .
find newtree -exec cvs add {} \;
cvs ci
Hmmm. I like this! Is it possible to use an import-less
approach like this one if top is one's home directory
(meaning that there will be a lot of other stuff there
besides newtree)?
Mike
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
