public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: Per Bothner <per@bothner.com>, overseers@sources.redhat.com
Subject: Re: switch to subversion?
Date: Sat, 20 Dec 2003 03:03:00 -0000	[thread overview]
Message-ID: <vt2wu8sgpnn.fsf@zenia.home> (raw)
In-Reply-To: <20031219114252.A60180@molenda.com>


Jason Molenda <jason-swarelist@molenda.com> writes:
> On Fri, Dec 19, 2003 at 11:38:01AM -0800, Per Bothner wrote:
> 
> > I don't know much about the internals and security implications
> > of either, and I'm certainly not volunteering for anything, but
> > curious what people think about the idea.
> 
> 
> I think anyone you talk to will be greatly interested in general
> (it'd be like asking "Who here likes kittens") but IMHO it's more
> trouble than you'd want for a big project at this point.  I don't
> know if any of the system maintainers really has the time to learn
> enough about svn and keep up to date on it to support an installation,
> and there will certainly be a need for support when it is first
> brought up.  Any group switching to svn will have a big cost of
> all the developers trying to re-learn their revision control system
> - even though I know the svn folks are trying to keep it similar
> to a cvs style RCS.

It may be worth mentioning that Subversion is not tied to HTTP,
WebDAV, and Apache.  There is an alternative protocol which tunnels
over ssh just like CVS does, and has a server which is much less
trouble to build, install, and maintain.

Subversion's main funding comes from a group very connected with
Apache, so despite the fact that the alternative protocol is really
much better as the standard access method, it's politically
impractical to highlight it too much.

  parent reply	other threads:[~2003-12-20  3:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 19:38 Per Bothner
2003-12-19 19:42 ` Jason Molenda
2003-12-19 19:48   ` Zack Weinberg
2003-12-19 20:09     ` Benjamin Kosnik
2003-12-19 20:23       ` Ian Lance Taylor
2003-12-20  3:08         ` Jim Blandy
2003-12-20  3:51           ` Zack Weinberg
2003-12-31 17:02         ` Andrew Cagney
2003-12-19 20:50     ` Joseph S. Myers
2003-12-19 22:25       ` Zack Weinberg
2003-12-20  3:05     ` Jim Blandy
2003-12-20  3:50       ` Zack Weinberg
2003-12-20  3:03   ` Jim Blandy [this message]
2003-12-20  3:14   ` Jim Blandy

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=vt2wu8sgpnn.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=jason-swarelist@molenda.com \
    --cc=overseers@sources.redhat.com \
    --cc=per@bothner.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 read-only IMAP folder(s) and NNTP newsgroup(s).