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

Re: Re: Automate backup of working copy

From: Lübbe Onken <luebbe.tortoisesvn_at_gmail.com>
Date: Mon, 1 Aug 2016 12:05:05 +0200

Hi Tim

2016-07-29 17:52 GMT+02:00 Tim Scott <tim.scott_at_oclc.org>:

>
> I don't like maintaining more than one version of a piece of code and
> branching means potentially working with another version of the same code -
> so I tend to avoid it.
>

Where's the difference between having a feature branch and copying your
working copy somewhere else using a tool like rsync? You work with more
than one version of the same code.

I see only advantages in using (a) feature branch(es). You can commit at
any time. Revisions are cheap and subversion keeps you sane, because it
takes care of the versioning for you. If you use rsync or anything similar,
how do you get back to the "almost" good version from yesterday that you
have overwritten in the mean time, but you'd like to reuse a piece of code
from there?

Cheers
- Lübbe

--
Please help me get more space on Dropbox :)
https://www.dropbox.com/referrals/NTIwMzcxNjI5
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net  PGP Key ID 0x23F511AB
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3180749
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-08-01 14:37:22 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.