We will certainly look forward to your patch which makes Subversion the most
compelling alternativ to CVS as I see it.
Much in line with your thoughts and from years of experience from a
project-centered environment handling around 25 projects a year, I believe
that an SCM provides the maximum overall benefit in a commercial environment
by combining the loose coupling of the copy-modify-merge source code
approach taken by CVS and Subversion together with decentralized
non-intrusize per-project meta-data and finally centralized statistics
allowing e.g. project managers and method & tools depts. to get an overall
view of e.g. repository status. While avoiding locks due to going on
holidays while having something checked out is a technical issue, it is
still an organizational issue to catch the guy doing that or maybe - as we
allow - taking charge of someone elses workspace, if necessary to get the
project moving.
best regards,
Jesper
-----Oprindelig meddelelse-----
Fra: Kumaran Santhanam [mailto:kumaran@tigris.org]
Sendt: 25. august 2003 17:58
Til: Greg Hudson
Cc: kfogel@collab.net; Jesper.Bork@eu.fkilogistex.com;
'dev@subversion.tigris.org'
Emne: Re: .svn directories
On Mon, 25 Aug 2003, Greg Hudson wrote:
> On Mon, 2003-08-25 at 10:44, kfogel@collab.net wrote:
> > Jesper Bork <Jesper.Bork@eu.fkilogistex.com> writes:
> > > directories. You could say that this reflects a lack of
> > > self-dicipline, but I believe that unless an even easier
> > > way of doing stuff like that exists, this is what people
> > > do.
...
> I don't think it's a very compelling argument, though. Won't these same
> people expect to be able to copy-paste from working directories and
> continue doing work? That only works if we have embedded .svn
> directories.
There are commercial solutions that do not have embedded
administrative directories. They simply provide a clean command
with which to copy/move workspace directories.
I intend to implement this in phase 2 of my patch. Phase 1 will
simply be getting the feature to work as a config file option. I
was thinking of a new command 'wc' (working copy)
It would go something like this:
User desires to copy workspace /home/user/venus to /home/user/mars :
1) cp -R /home/user/venus /home/user/mars
2) svn wc copy /home/user/venus /home/user/mars
3) svn wc list
/home/user/venus
/home/user/mars
User desires to move workspace /home/user/venus to /home/user/mars :
1) mv /home/user/venus /home/user/mars
2) svn wc move /home/user/venus /home/user/mars
3) svn wc list
/home/user/mars
User wishes to remove a workspace from control :
1) svn wc remove /home/user/venus
User wishes to edit the working copy list:
1) svn wc edit
[Opens editor with the following text]
/home/user/venus -> (REPO URL)
/home/user/mars -> (REPO URL)
2) user can manipulate the left side of the mapping
An intended side-effect of separated meta directories is the fact
that you can get global information about all of your workspaces
at once. This is a common features in popular commercial SCM
solutions, and one which I have found extremely useful.
Regards,
Kumaran
Received on Tue Aug 26 17:03:20 2003