[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: Will Appleton <wfappleton_at_gmail.com>
Date: 2007-09-12 18:29:04 CEST

On 9/11/07, Andy Levy <andy.levy@gmail.com> wrote:
> On 9/11/07, Tim Uckun <timuckun@gmail.com> wrote:
> > >
> > > 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.
> >
> >
> > In my case I am dealing with SVN as a sort of a document management
> > platform. I am dealing with typical office workers and not
> > programmers. I have used ifolders before. It's basically an automated
> > tool to sync content with a central server (like subversion) but it
> > does not offer version control.
> >
> > If Tortoise was to automatically do an update and commit every N
> > minutes then it would have all the features of ifolders and many many
> > more plus it would be faster. That's why I put in the feature request.
> >
> > The auto-locking would be icing on the cake. My primary wish is that
> > the whole update, commit cycle would be automatic, run on a schedule
> > and only make it self known if there were errors (otherwise silent).
> If the auto-locking isn't mandatory, then just mount the repository
> via WebDAV and give everyone a mapped drive. It's more or less meant
> for what you're looking to do. As for updating a "server" somewhere,
> just have a scheduled task update a working copy on that server (I
> assume read-only for everyone else) on a regular basis. But I kind of
> wonder whether you need to do that at all, when you could just point
> people at the WebDAV-mounted drive or even an HTTP URL to browse the
> contents realtime.
> Really all of this is well outside the realm of TSVN, it's more a
> Subversion server/config issue.

If you want the auto-update without the WebDAV, you could just add an
"at" job that does an svn up from the command line (assuming you're on
Windows). Use cron on Linux/UNIX to accomplish the same thing.

Is having users update and commit really a problem or is this just to
fix an anticipated problem? We have about 20 business analysts and
project managers using TSVN to manage documents and so far there
haven't been any issues that couldn't be resolved with about 10
minutes of training.


To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Sep 12 18:29:41 2007

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