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

Re: Communication of CHANGES

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-11-30 18:38:47 CET

On 11/30/07, kmradke@rockwellcollins.com <kmradke@rockwellcollins.com> wrote:
> "Matt Sickler" <crazyfordynamite@gmail.com> wrote on 11/29/2007 08:38:20
> PM:
> > If you are so hellbent on getting this feature (or featurecreep) added
> > to the core subversion library, why havn't you spent this time hacking
> > away at the subversion sources yourself? Its not like they are closed
> > source or anything.
> >
> > The subversion devs have already asserted that they dont want to put
> > something into core unless its absolutely necessary.
> > This would fall in the category "Feature that would be nice to have,
> > but I can get along just fine without it"
> In an open source project, it is always beneficial to get "buy in" from
> the main developers before working on a patch to make sure the
> functionality
> is something they would accept. I am never a fan of forking a project.
> Most of this discussion has been more of a misunderstanding of the
> intended use cases.
> We have users that would benefit from some of the proposed information,
> but they are still able to work (less productive) with the current
> implementation.
> We also could implement SVN functionality with a bunch of scripts on
> top of RCS. Should we? Absolutely NOT!

Sorry, but it's been tried before. It's NOT possible :-)

> Why do we use SVN? Because it makes us more productive!
> Can SVN be made more productive and better? YES!
> Will all new SVN features be absolutely necessary for me? Probably not,
> but
> I'm ok with that. People have different use cases.

Couldn't resist!



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 30 18:43:22 2007

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.