From: David Brown <git@davidb.org>
To: Steven Grimm <koreth@midwinter.com>
Cc: 'git' <git@vger.kernel.org>
Subject: Re: Subversion developer: svn is for dumb people
Date: Thu, 18 Oct 2007 09:57:11 -0700 [thread overview]
Message-ID: <20071018165711.GA24460@old.davidb.org> (raw)
In-Reply-To: <47176CE0.7030609@midwinter.com>
On Thu, Oct 18, 2007 at 07:25:36AM -0700, Steven Grimm wrote:
> 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. I find code reviews
> *harder* in a centralized system because you end up building external tools
> to help people try out each other's changes.
The review comment is completely bogus. Centralized systems, at least like
SVN and P4 encourage a check-it-in-deal-with-the-problems-later attitude.
The tool discourages you from trying out other's changes, whereas a DVCS
tends to have lots of little branches and easy migration between them.
I think this is less an issue of distributed or not, but more that branches
are just so expensive in most other revision control systems. Whether that
is expensive in resource, or just in understanding what is going on (for
example, requiring users to track merge ancestors is rediculous).
David
next prev parent reply other threads:[~2007-10-18 16:57 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 [this message]
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
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=20071018165711.GA24460@old.davidb.org \
--to=git@davidb.org \
--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).