From: Pierre Habouzit <madcoder@debian.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Steven Grimm <koreth@midwinter.com>, 'git' <git@vger.kernel.org>
Subject: Re: Subversion developer: svn is for dumb people
Date: Fri, 19 Oct 2007 15:19:34 +0200 [thread overview]
Message-ID: <20071019131934.GD4404@artemis.corp> (raw)
In-Reply-To: <Pine.LNX.4.64.0710191514190.16728@wbgn129.biozentrum.uni-wuerzburg.de>
[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]
On Fri, Oct 19, 2007 at 01:17:05PM +0000, Johannes Schindelin wrote:
> Hi,
>
> On Fri, 19 Oct 2007, Pierre Habouzit wrote:
>
> > On Thu, Oct 18, 2007 at 02:25:36PM +0000, Steven Grimm wrote:
> > > Thought folks here might get a kick out of this:
> > >
> > > http://blog.red-bean.com/sussman/?p=79
> > >
> > > Okay, my summary is slightly facetious, but that's basically the gist
> > > of what he's saying: you should choose Subversion rather than a DVCS
> > > because most of your users won't be smart enough to use the better
> > > tool.
> > >
> > > I can't say he's completely wrong, especially about the 20/80% idea
> > > (though I think "20%" is generous), but some of his specific arguments
> > > about DVCS are on the bogus side. "Centralized systems encourage code
> > > reviews," for one -- I challenge him to find a project with a more
> > > pervasive and effective code-reviewing culture than the git project.
> >
> > Your argument is also bogus.
> >
> > IMNSHO, peer reviewing has nothing to do with git, svn, or $SCM. It's
> > a social pattern. There are people that do it because they understand
> > it's a good and necessary sound thing to do, and there are the others.
> > Guess what, it has a lot to do with the 20%/80% line (that I would have
> > more described as the 2/98 but well…).
>
> I tend to disagree. Git at least _enables_ you to have the
> one-committer-per-repository scheme, it even _encourages_ it to a certain
> extent.
>
> And once you go that route, it is easy to see that the committer says "I
> will not let that _crap_ enter my repository." Bingo, peer review.
>
> Compare that to a centralised repository, where more often than not, the
> administrator is not even part of the developer community! It is much
> easier not to feel too responsible for the code you are committing there.
I agree, that's why I said that git made it easier. WHat I pretend to
be wrong is to say that a SCM will make people review code or not. Git
merely help people that want to always review code to be completely sure
some review has happened before the code is merged. But nothing in git
forbids you to use the big fat <centralized repo with everyone having
push access to it>-mode.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-19 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 14:25 Subversion developer: svn is for dumb people Steven Grimm
2007-10-18 16:57 ` David Brown
2007-10-18 18:33 ` Jeff King
2007-10-18 22:40 ` Sam Vilain
2007-10-19 11:34 ` Pierre Habouzit
2007-10-19 13:17 ` Johannes Schindelin
2007-10-19 13:19 ` Pierre Habouzit [this message]
2007-10-19 12:10 ` Andy Parkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071019131934.GD4404@artemis.corp \
--to=madcoder@debian.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=koreth@midwinter.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).