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

Re: Delete *for real* from a repository

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Thu, 17 Sep 2009 15:21:23 -0400

David Weintraub wrote:
> However, I find major problems with GIT when you are working in a commercial
> environment. First of all, each copy of the GIT repository requires a
> particular person to be the gatekeeper whether or not to accept changes in
> their copy. That means that person is responsible for merging all changes
> into that copy of the repository. The last place which used Git made me, the
> SCM who is not a developer, the person responsible for handling all the
> merging since the developers didn't want to do it themselves. Hilarity
> ensued.

I see no such problem. All git clients can have a reference to a
'master' repostiroy, against which their changes can be compared and
merges made locally, and in fact can have configured references to
secondary and tertiary repositories for particular features. I set up
exactly this last spring for someone who works on his laptop going to
and from work, and with various contributors, so that each of us could
do our work remotely, *record changes remotely as individual changes*,
push them back to our development "branches" on the centralized
repository, and the project lead could approve or reject individual
sets of changes to the master.

> I can see why GIT is popular and why Linux uses it, but I don't see a
> distributed repository as the bright shiny future of revision control.

See above as an example of one of its features. I find git to be
easier to secure, and not prone to the "store passwords in clear-text"
problem of Subversion's UNIX and Linux default clients. It also
permits off-line changes to occur, and to be stored locally. For
systems (such as configuration files for complex software that may be
offsite, especially security or network configuration files), this is
very useful.

The integrated tag-signature utility is very useful for code releases:
so is the much, much better integrated security model of the dedicated
shell for SSH access, rather than the more complex and fragile
svn+ssh. If there weren't such a legacy of old CVS and now Subversion
projects, I'd have discarded Subversion last spring.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-17 21:22:12 CEST

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

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