[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: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Thu, 7 Jul 2011 09:31:31 +0100

On 7 July 2011 06:43, Markus Schaber <m.schaber_at_3s-software.com> wrote:
> Hi, Craig,
> Von: Craig [mailto:shadycraig_at_gmail.com]
>> 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.
> This sounds like a typical use case for a distributed VCS like GIT or
> Mercurial.
> Maybe the aforementioned SVK can help here, too.
> But I'm afraid that using SVN for this workflow won't work without
> cludgy workarounds.

I believe SVK is no longer being developed. SVN cannot handle offline
commits, so as Markus says, a DVCS seems the better way to go.


:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-07-07 10:31:41 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.