info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: what is the opposite of "cvs import"


From: Jesus Manuel NAVARRO LOPEZ
Subject: Re: what is the opposite of "cvs import"
Date: Wed, 16 Jan 2002 12:50:29 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901

Hi Patrick:

Patrick K wrote:

hi i am new to cvs and am having a problem figuring
this out:

what is the opposite of "cvs import"?



Well, someone would say either "cvs export" or "tropmi svc"


it seems to me that the effect of "cvs import
repository vendor-tag release-tags" is to create a
repository in the home/CVS/repository directory.



Wouldn't say that: *cvs init* purpouse is to create a repository in the home/CVS/repository directory, while import's goal is *import* third party sources to a properly inited repo. What might confuse you is the fact that when you init a repo and you already has some files you want to put under its control you import them too, since for the repo they are alike to any other "third party sources".


now how do i get RID of everything just created? how
do i turn back the clock? do i just delete
home/CVS/repository/* and rmdir home/CVS/repository
???



If you delete all the files that "make" a CVS repository, you effectively has "deleted" the repo, so, somehow, yes. Now, letting appart your case (that is, just doing some tests on a newly created repo) the way to go if you want to "revert" your repo to a given state in the past is using labels: just as in "the real world" there's no way to go back in time you shouldn't do it on any SCM tool since then you loose part of your repo's history (and having that history is the esence of any SCM in first place). What you *really* are doing (so what you want to preserve as your repo's history) is something like this:
Step 1: inited the repo
Step 2: populated with this and that file
Step 3: some modifications
Step 4: more modifications -- ACHIEVED MILESTONE 1
Step 5: some more modifications
Setp 6: Not glad with modifications on Step 5 so I make *some more modifications which are exactly the same (only backwards) that in Step 5* -- ACHIEVED MILESTONE 2 (which casually puts all the files alike to how they were in MILESTONE 1)

Note that this is not the same repo history than the following one:
Step 1: inited the repo
Step 2: populated with this and that file
Step 3: some modifications
Step 4: more modifications -- ACHIEVED MILESTONE 1


...which would be the result of "deleting" steps 5 and 6.
You would loose the step 5, so you'd never know that you failed with it, thus the knowledge of this fact, and its analisys (so why you failed in order to avoid that in the future).

With all this in mind you will be able to find your answer by yourself looking at the manuals.
--
SALUD,
Jesús
***
address@hidden
***



reply via email to

[Prev in Thread] Current Thread [Next in Thread]