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

Re: How to delete all unmodified files between 2 revisions on a patch branch?

From: Stefan Kueng <tortoisesvn_at_gmail.com>
Date: Sat, 27 Dec 2008 15:31:40 +0100

AfterShock wrote:
> Hi Guys,
>
> I'm releasing a patch to a freeware online game. Typically our release
> process goes something like:
>
> - Create a 'patch 2.2' branch from HEAD
> - Checkout this branch to a new folder locally
> - Checkout the tagged 'patch 2.1' branch to another new folder locally
> - Use winmerge or similar to comapre which files have changed between the
> two
> - Manually SVN delete any files which haven't changed from the patch 2.2
> branch
>
> Now we're dealing with thousands of files, this becomes not only time
> consuming and tedious, but also prone to error. There must be some built-in
> method of creating a branch that only contains the files modified between 2
> revisions - is there?

* Repository browser
* browse to "patch 2.1"
* right-click on "patch 2.1", choose "mark for comparison"
* browse to "patch 2.2"
* right-click on "patch 2.2", choose "compare urls"
  --> this brings up the "changed files" dialog, showing all
      files/folders which have changed between those two urls
* select all files (Ctrl-A), right-click, choose
  "export selection to..."

> Alternatively, is there a method of SVN deleting all files that are
> unmodified since revision X?

No, such a feature does not exist.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=993755
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].

Received on 2008-12-27 15:31:57 CET

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

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