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

RE: Update to revision

From: Andreas Nicolai <andreas.nicolai_at_gmx.net>
Date: Sat, 2 Feb 2013 01:07:51 -0800 (PST)

Hi all,

I'd like to bring up the old discussion about the "Update to date" feature. While I understand Stefan's reasoning about the potential dangers, there seems to be a use case for many users (at least several programmers that I know of) who develop projects with externals where both externals and the project itself are in the trunk development (example: the main project is merely split into two projects for adminstrative/packaging reasons, but otherwise it is the same project). In our projects, we sometimes have 4 applications that are concurrently developed and they share up to 12 libraries via svn:externals. The manual tagging/branching does really only work towards the end of a project, or with a significant overhead which does not pay off for us.

In such use cases it is definitely a relevant wish to have a revert-to-date feature, which could be implemented in the GUI of TortoseSVN alone and does not require changes in the svnlib.

Suggested behavior:
- user selects "revert to date" and can enter a date/select a date from the svn-log for that project
- the dialog offers a checkbox "Revert externals to same date?" with the appropriate warnings from Stefan about unsafe project states and the recommendation that a formal update-to-head should be done again afterwards. Optionally, the dialog may offer a list of external repositories (just like in the branch/tag dialog), so that the user can select individual externals to "revert-to-date"
- upon accepting this dialog, TortoiseSVN reverts the main project repository (so far same functionality as the regular revert-to-revision dialog)
- then, a list of externals in that revision is obtained
- from the originally selected externals, all svn:externals are removed (with a log warning) that did not exist back then
- now each of the external log files is queried to determine the corresponding rev at the desired date
- each external is reverted to that rev (again, standard behavior)

The implementation is not really trivial, but not too complicated either. Maybe we can have a poll or so to get an idea about the priority.

If the availability of a developer is the main problem, I could work on this implementation beginning in May (I did some changes in TortoiseSVN long time ago, so I hope I'll get this done).


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-02-02 10:08:42 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.