info-cvs
[Top][All Lists]
Advanced

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

Re: CVS newbie seeks advice on tag management


From: Doug Poland
Subject: Re: CVS newbie seeks advice on tag management
Date: Wed, 27 Feb 2002 13:11:32 -0600
User-agent: Mutt/1.2.5i

On Tue, Feb 26, 2002 at 08:32:38PM -0500, George J. Schlitz wrote:
> I'm a relative CVS newbie to, but this sounds pretty straightforward, if I
> am understanding.  Feel free to take others' advice if any of the more
> experienced experts give you any :)
> 
> Assuming your repository directory is Acme-sql:
> 
> 1)After working on and completing "Live-01" (doing commits of changes,
> testing, and finally running the scripts at the client, etc.), tag the
> appropriate files with tag name "Live-01":
> cvs tag Live-01 010-create_stored_proc.sql 020-alter_table.sql
> 030-delete_orphans.sql
> 
Ok, I've done that

> 2)I tend to "release" (the cvs command "release" that removes working
> copies) my working directory after I am done working- this way, all working
> copies are removed (hopefully all changes have been committed) and it makes
> it easier to get what I want later:
> cvs release -d Acme-sql
> (make sure you aren't in the directory when you release it- all this does is
> clean your work area)
> 
What I've been doing is rm *sql in the working directory.  So the CVS directory
is still there.

> 3)Now you can always get this release of code by:
> cvs checkout -r Live-01 Acme-sql
> (This will always get the versions of files in Acme-sql with the tag
> "Live-01"
> 
That works for me.

> 4)Next- develop the Live-02 scripts, test, run at client.  When ready to
> tag:
> cvs tag Live-02 010-add_menu_options.sql 020-create_table.sql
> 030-alter_stored_proc.sql 040-delete_old_menus.sql
> 
This is where I'm having problems.  I create the new files but cannot add 
them to the repository.  I get the message 

        "Cannot add file on non-branch tag Live-02"

> 
> I hope this helps!
>
Thanks so far, just can't get beyond this part :(



> George
> 
> -----Original Message-----
> From: address@hidden [mailto:address@hidden Behalf Of
> Doug Poland
> Sent: Tuesday, February 26, 2002 5:37 PM
> To: address@hidden
> Subject: CVS newbie seeks advice on tag management
> 
> 
> Hi,
> 
> I'm very familiar with RCS but new to CVS.  After searching
> through the docs and mail archives, I'm at a loss as how to
> best use CVS in the following scenario.
> 
> I'm managing a SQL Server application through the use of
> .sql script files.  I work in "batches" or "releases" as
> dictated by client needs.  For example, I may have the
> following files for my "Live-01" release:
> 
>       010-create_stored_proc.sql
>       020-alter_table.sql
>       030-delete_orphans.sql
> 
> Some weeks later, I have more to do on the project and
> it turns out that I need the following scripts (Let's call
> it Live-02):
> 
>       010-add_menu_options.sql
>       020-create_table.sql
>       030-alter_stored_proc.sql
>       040-delete_old_menus.sql
> 
> I want to save all my scripts in a single repository, say
> Acme-sql.  After I've run the Live-01 code at the client,
> I won't need the files in Live-01 anymore.  However, I want
> be able to access them so I can cut/paste code between the
> two releases.
> 
> So basically I want the release I'm calling Live-01 to
> contain only those files listed.  I want the release Live-02
> to contain only the new files.  As stated earlier, I still
> want to pull out Live-01 from the repository.
> 
> Can someone point me to a FAQ or doc that deals with management
> strategies?  Or, outline the steps (tag this branch, remove those
> files, etc) I should take.  Please note that I'm a newbie with
> CVS and my use of the terms "tag" and "release" might be erroneous.
> 
> Many thanks for your help.
> 
> --
> Regards,
> Doug
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
> 
> 

-- 
Regards,
Doug



reply via email to

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