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.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2786676
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-07-07 01:41:28 CEST