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

Re: Feature request.

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-09-12 03:57:32 CEST

On 9/11/07, Tim Uckun <timuckun@gmail.com> wrote:
> >
> > If you serve your repository via Apache and mount it as a WebDAV
> > drive, you'll get most of those features out of the gate. Only thing
> > you wouldn't get is auto-locking.
>
> That's very insteresting. I hadn't thought of that. I would prefer to
> have the files locally on my machine but it's worth giving it a go.

If you're auto-committing all the time, what's the difference? You'll
need to be connected all the time anyway. And it doesn't stop you from
performing a real checkout to work offline, and commit the changes
when you're back in the office or whatever.

> I would still like you to consider an autoupdate/autocommit option on
> the tsvn client though. It could also be handy for automatically
> deploying your application to servers and whatnot.

And a royal pain in the a** when you decide that your last change
wasn't really what you wanted to do and you need to do a merge or copy
in the repository instead of a real simple revert to undo it (because
it was auto-committed).

Deploying to servers should never be automatic IMHO, it should be part
of a controlled release management process, continuous integration, or
even a hook script that triggers under certain conditions.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Sep 12 03:54:01 2007

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.