[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Commiting the whole project with a different tag name?
From: |
Donald Sharp |
Subject: |
Re: Commiting the whole project with a different tag name? |
Date: |
Wed, 30 Jan 2002 14:30:48 -0500 |
User-agent: |
Mutt/1.2.4i |
Why all this work? Why not just have a development branch
and a release branch? What are you trying to do?
donald
On Wed, Jan 30, 2002 at 01:39:08PM -0500, Datla, Raghav wrote:
> Hi,
>
> I have a project under CVS and we are going for production in the near
> future.
> Once the code in Present Repository is ready for production, I will create
> another Repository for production code (which will just contain production
> code, so that there will not be any intervention from users) and will commit
> the code into production Repository with some tag name.
>
> If we get another release after two months for the same project, Will it be
> possible to commit the new code into the Production Repository with some new
> tag name without any conflicts with the existing Release code in the
> repository?.
> Will I be able get the old code by just specifying the tag name if it is
> required as a backout procedure once I commit the new release code?.
>
> Thanks Inadvance,
> -Raghav
>
>
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs