On Thu, Mar 3, 2011 at 08:47, Felix <fb_at_ltec.ch> wrote:
> On 03.03.2011 14:40, Robin Guest wrote:
>> On 3 March 2011 13:34, Felix <fb_at_ltec.ch <mailto:fb_at_ltec.ch>> wrote:
>> On 03.03.2011 12:39, Felix Saphir wrote:
>> > Am 03.03.2011 12:26, schrieb Felix:
>> >> I use Tortoise SVN 1.6.12 on windows. After a recent upgrade
>> from Debian
>> >> Lenny to Squeeze (including an upgrade of SAMBA from 3.2.5 to 3.5.6)
>> >> checkouts to shares on the SAMBA server fail with a message
>> similar to this:
>> > [...]
>> >> Can anybody give me hint about what I should try next, including
>> changing a
>> >> setting of the SAMBA server that is probably known to create
>> trouble with
>> >> Tortoise SVN?
>> > Simple: Don't do that. Don't put working copies on network shares and
>> > don't share working copies between operating systems.
>> > Felix
>> I do not share working copies between different operating systems.
>> The reason for which they are on a network share is backup.
>> I suggest keeping your repository local, and using scheduled svnadmin
>> hotcopy http://svnbook.red-bean.com/en/1.0/re33.html to backup to your
>> network location.
>> But a far, far better solution would be to set up an svnserve or apache
>> webdav server on your server. Svnserve is so simple, I wonder why so
>> many people are determined to resist using it.
> Of course I have a SVN server running. But the SVN server is not a sort
> of 'backup server', i.e. I do not want to commit something just for
> being backed up.
It's more than just "backup" - incremental commits will allow you to
roll back a change that didn't work properly. If you make a week's
worth of changes, and discover that a change you made on day 3 breaks
things, you can't easily go back and undo that.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-03-03 14:50:35 CET