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

A "new working copy" question (request)

From: Miha Vitorovic <mvitorovic_at_nil.si>
Date: Mon, 28 Apr 2008 10:04:40 +0200

Hi all,

Some background first:
The talk about the new Subversion working copy and a common area for all
Subversion related data is making me quite excited -- we develop mostly in
Lotus Notes/Domino which has a really shitty VCS, not to mention
development client. So we started using Eclipse along with Subversion as
our version control system. But since everything in Domino is stored on
the server, that meant exporting everything to disk, developing in
Eclipse, using svn and putting everything back into Domino to test it.
It's not such a big deal once you get used to it, but things are
changing... For start Notes client has been ported to the Eclipse
platform, and the developer client is about to follow. Which could mean
being able to use Subclipse for version control system directly in the
client, if SVN didn't assume that files are on the disk and insist on
creating the .svn directories all over the place. So, being able to put
all the .svn stuff in one place and away from the source seems just like
something that one would need to integrate SVN with Domino. That, and the
ability to read the files under version control from anywhere, not just
the disk.

What I'm trying to say is, if you're going to rewrite the working copy
library, maybe create a special access layer for the working copy also, so
that people might be encouraged to add additional data sources [with the
disk being default and only one supported, of course].

Thanks and best regards,

  Miha Vitorovic
  Inženir v tehničnem področju
  Customer Support Engineer
   NIL Data Communications,  Tivolska cesta 48,  1000 Ljubljana,  Slovenia
   Phone +386 1 4746 500      Fax +386 1 4746 501     http://www.NIL.si
Received on 2008-04-28 10:04:58 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.