[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Tagging Policy Full & Patch Release

From: Lakshman Srilakshmanan <lakshman.srilakshmanan_at_tradingpost.com.au>
Date: 2006-02-22 07:40:05 CET

Hi Steve,

Thanks for your feedback.

svn diff URL_of_Release_1_0_0 URL_of_Release_1_0_1 -- lists all the
changes. This could serve as a work around to my requirement.

I was actually hoping
  1) to have just a list of files that changed between the two Releases
  2) extract all files that have changed.

Is either of the above possible ?

Finally, even though I can identify the difference, How do I create
(patch create command) a Patch file and Apply it to Release-1.0.0.


-----Original Message-----
From: Steve Williams [mailto:stevewilliams@kromestudios.com]
Sent: Tuesday, 21 February 2006 5:18 PM
To: Lakshman Srilakshmanan
Cc: users@subversion.tigris.org
Subject: Re: Tagging Policy Full & Patch Release

Lakshman Srilakshmanan wrote:

>Hi All,
>I would like to explain the tagging process I followed in CVS and would
>much appreciate an alternative approach in Subversion.
>When I do a full release of an application I tag the entire application
>in CVS as Release_1_0_0
>When I do a patch release of an application (ie 3 files) I tag the
>entire application in CVS Release_1_0_1 and another tag Patch_1_0_1
>containing ONLY the 3 files that will be released.
>The rational behind this tagging policy is that I can re-create the
>entire package based on Release_1_0_1 (if needed) and can apply only
>patch into production using Patch_1_0_1.
>In Subversion I can create a full Release tag Release_1_0_1. But I
>believe I can create a Patch_1_0_1 tag as described above. Or am I

Patch_1_0_1 would essentially be

svn diff URL_of_Release_1_0_0 URL_of_Release_1_0_1

This would give you a patch of the differences between the two
releases. Apply this patch to a source tree of Release_1_0_0 and you
will have an exact copy of Release_1_0_1.

This message and its attachments may contain legally privileged or
confidential information. This message is intended for the use of the
individual or entity to which it is addressed. If you are not the
addressee indicated in this message, or the employee or agent
responsible for delivering the message to the intended recipient, you
may not copy or deliver this message or its attachments to anyone.
Rather, you should permanently delete this message and its attachments
and kindly notify the sender by reply e-mail. Any content of this
message and its attachments, which does not relate to the official
business of the sending company must be taken not to have been sent or
endorsed by the sending company or any of its related entities. No
warranty is made that the e-mail or attachment(s) are free from computer
virus or other defect.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 22 07:41:07 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.