Comments on: Using TortoiseSVN to Export Only New/Modified Files

By: Jason

Jason — Thu, 01 Dec 2011 19:14:23 +0000

very cool – thanks!

By: Claudio

Claudio — Thu, 01 Dec 2011 18:58:50 +0000

Using Script to Export Only New/Modified Files from SVN revision

http://www.jroller.com/vagheti/entry/using_script_to_export_only

By: Rude

Rude — Fri, 02 Sep 2011 08:26:29 +0000

Thanks a lot, man. I would have expected this function rather in the create-patch dialog.

By: How To Determine What Files Have Changed Between Two Subversion Revisions « Derek Reynolds – Brain Dump-O-Matic

Sat, 20 Aug 2011 17:05:21 +0000

[...] Source Advertisement GA_googleAddAttr("AdOpt", "1"); GA_googleAddAttr("Origin", "other"); [...]

By: xrigher

xrigher — Wed, 13 Jul 2011 12:19:42 +0000

thx a lot! this is what exactly i wanted.

By: amila

amila — Fri, 01 Jul 2011 12:36:08 +0000

Hi,
Nice post. Thanks.

I wanted to do this by using command line. If can please post command for that.

By: Jason

Jason — Wed, 16 Mar 2011 21:16:20 +0000

hey Kamil, i probably don’t fully understand your workflow but you might consider looking into svn tags for these purposes. you can all just check into the head revision without branching and then upon approval you can tag changes for your release.

however, what you are describing does sound exactly like what git does. you can have tree-like hierarchy of repositories. it’s a slightly different concept. branching is a normal, expected part of git workflow and is meant to be seamless. i have a feeling what you are trying to do is perfect use case for git.

By: Kamil

Kamil — Wed, 16 Mar 2011 19:23:11 +0000

Jason, thx for your reply. As I have written above I know there is branching functionality in SVN and I know how does it work, but I’m nor sure if creating branches for small tasks (1-3 days of development) is good idea.

Let me explain my problem in more details. My Team is build of 5 developers, during a week (5 days) each of them is working over 2-4 tasks. So it would give us 10-20 branches in SVN repository. Most of all some tasks takes more then 5 days, so please imagine over 20 opened branches in repository – IMHO it might be little difficult to maintain and it would make repository to rapidly grow up.

What I would like to do is to export modified files from my WC to easily upload them to draft server. After the changes are confirmed by client the developer would commit them to repository and upload to production.

Once again, I know branches perfectly fits to what I described above, I’m just wondering if they are required for such a small tasks. Export modified files from WC would fix my problem

By: Jason

Jason — Fri, 11 Mar 2011 08:44:25 +0000

Hey Kamil you have several options for working that way from simply making a backup copy of your new work to branching.

Branching seems like the correct way based on what you said, but a simple backup copy could be ok if you don’t want version control for your new changes before you are ready.

You might look into git also, it is meant to do lots of branching easily.

By: kbalcerek

kbalcerek — Thu, 10 Mar 2011 08:39:01 +0000

Hello,

Same question as above, is it possible to do it with WC and not commit changes? I know we can drag&drop files from “Check for modifications” dialog, but in this way folders structure is not saved.

The other option is to create patch, but as far as I have noticed patch does not contain binary files.

What I would like to do is to copy modified/added/non-versioned files to some folder, revert changes on my WC so I could do some other changes and then get back to my problem later copying previously saved folder and overwriting files in my WC. I know there is a branch functionality, but I don’t want to make mess in repository (I thing creating branches for small tasks managed by one developer is not good idea, em I right?)

Kamil