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

Re: Strategy for working offline (commit/tag)

From: Ron Wilson <ronw.mrmx_at_gmail.com>
Date: Wed, 6 Jul 2011 19:41:17 -0400

On Wed, Jul 6, 2011 at 10:10 AM, Craig <shadycraig_at_gmail.com> wrote:
> In my organisation the workflow is that each software build must be
> tagged, also any changes to the code base need to be committed back.
> Soon I expect it'll be necessary to build without access to the
> subversion server and clearly the commit and tag are impossible.
> How can this be addressed?
> One idea I had was to make a copy of the entire working copy for
> tagging later.
> Another was to take a local copy of the repository and later merge in
> the new revisions.

Making copies of the working copy is easy, but you will need to
restore only your working files, not the SVN files. Probably best to
not copy the SVN files

SVK is a tool for using SVN as a distributed VCS, but I have not used
it, so I don't know how it works with TortoiseSVN.

If you opt to manually maintain a local copy of the repository, your
best option would be to have a seperate working copy for the local
repository that you use for your off-line development. When you are
ready to commit your local changes to the main repository, you export
your fist local commit since you last syncronized to your main working
copy, do the commit, then export the next local commit, and so on.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-07-07 01:41: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.