• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Site management strategies with Subversion
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Site management strategies with Subversion


  • Subject: Re: Site management strategies with Subversion
  • From: wojingo <email@hidden>
  • Date: Tue, 14 Mar 2006 11:53:44 +1030

Hi,


email@hidden wrote:
The problem is, Subversion doesn't have an official tag command. The "svn way" to do tags is to take a snapshot of the current state of the repository, by making a copy of it in a special /tags directory. That means, I think, that there is no way to tag-and-move only part of a repository - it is always going to be all or nothing. This will be fine for the way you work, but it throws a huge monkey-wrench into the way I work.

Anyone else have any thoughts here? Is there a more clever workaround than splitting things up into a gazillion little repositories?



I was wondering if you have read the book available on the svn website?
This is a section about tags that seems relevant.

Creating a Complex Tag

Sometimes you may want your “snapshot” to be more complicated than a single directory at a single revision.

For example, pretend your project is much larger than our calc example: suppose it contains a number of subdirectories and many more files. In the course of your work, you may decide that you need to create a working copy that is designed to have specific features and bug fixes. You can accomplish this by selectively backdating files or directories to particular revisions (using svn update -r liberally), or by switching files and directories to particular branches (making use of svn switch). When you're done, your working copy is a hodgepodge of repository locations from different revisions. But after testing, you know it's the precise combination of data you need.

Time to make a snapshot. Copying one URL to another won't work here. In this case, you want to make a snapshot of your exact working copy arrangement and store it in the repository. Luckily, svn copy actually has four different uses (which you can read about in Chapter 9), including the ability to copy a working-copy tree to the repository:

$ ls
my-working-copy/

$ svn copy my-working-copy http://svn.example.com/repos/calc/tags/mytag

Committed revision 352.

Now there is a new directory in the repository, /calc/tags/mytag, which is an exact snapshot of your working copy—mixed revisions, URLs, and all.


regards, - shaun _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Site management strategies with Subversion
      • From: email@hidden
    • Re: Site management strategies with Subversion
      • From: Chuck Hill <email@hidden>
References: 
 >Site management strategies with Subversion (From: email@hidden)
 >Re: Site management strategies with Subversion (From: Zak Burke <email@hidden>)
 >Re: Site management strategies with Subversion (From: email@hidden)
 >Re: Site management strategies with Subversion (From: Zak Burke <email@hidden>)
 >Re: Site management strategies with Subversion (From: email@hidden)

  • Prev by Date: Re: Site management strategies with Subversion
  • Next by Date: Re: Site management strategies with Subversion
  • Previous by thread: Re: Site management strategies with Subversion
  • Next by thread: Re: Site management strategies with Subversion
  • Index(es):
    • Date
    • Thread