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

Changes from 1.5 to 1.6

From: Branden Visser <branden_at_uwindsor.ca>
Date: Thu, 21 May 2009 04:42:50 -0700 (PDT)

Hi everyone, this is my first post, so before I report any issues, I'd like to send an up-front thanks for a great product -- Thank You!

I noticed when updating my Windows TortoiseSVN client from 1.5 to 1.6, there were some changes that impacted my typical workflow of the client. I work on a large software system that is a collaboration of many smaller subprojects (100+). When we have an issue, I create a ticket in our call-tracking system (JIRA), and create a branch to manage changes to that ticket.

Here is how I manage this with SVN:

1. A new ticket is created (say it's TCK-1), I create a new branch directory called TCK-1.

2. Since this ticket will only require changes to 1 or 2 of the sub-projects, I only branch those that are necessary. So I branch the projects that I need to change into the TCK-1 branch. A total check-out of the entire project is over 20min and greatly impacts my productivity (and diskspace).

3. Make changes that I need, commit them to the branch.

4. When testing and everything is complete, merge changes to those projects back into the trunk.

There are a few changes which seem to affect this process:

After branching the subprojects in step #2, I can no longer use SVN-update in the branch group to "Check-out" the projects into the ticket's branch directory. I need to use repo-browser to "check-out" the directories individually -- but when I do that, there doesn't seem to be any link between the ticket's branch directory and the subject directories beneath it (e.g., if I make a change to one of the subprojects, the icon overlays aren't displayed on directory TCK-1). I would need to completely delete the TCK-1 directory and check it out in its entirety in order for there to be cohesion between it and its children.

I have run into other similar issues with the parent not being linked to its children (conflict handling and reverting can be funny when doing so at the TCK-1 level in the example above).

Was the process of "checking-out" a newly-added subfolder under a parent changed from being able to do a simple update? Is my work flow a use-case that would be considered when changes are made to the client in newer versions?

Any help is appreciated.

Thanks for reading,



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-05-21 14:50:28 CEST

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.