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

Re: [OT] commit methodology

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-03-30 02:37:51 CEST

On Thu, Mar 29, 2001 at 05:23:37PM -0600, Karl Fogel wrote:
> +1
>
> (When I said "please don't break 'make check'" in my previous mail, I
> meant that how you do that is up to you. Whether you run the test
> suite before every commit is your business -- a matter of personal
> policy. Only when the rest of us start being affected do we get the
> right to nose in. :-) )

Right! :-)

>...
> Greg Stein <gstein@lyra.org> writes:
> > This is a bit off-topic for this list, but what the heck. IMO, yes, people
> > can/should be able to check in stuff according to whatever guidelines they
> > care to impose upon themselves.

Oh, and a bit of backfill here. The above comment assumes that the developer
is capable and responsible :-). Personally, I tend to always trust anybody
with commit access (which sets a bar right there), and let them do their
work as they see fit.

Trust is a big thing for me. If developers don't trust each other to do the
right thing, then the whole project loses productivity. I can go on about
this forever, but the main point here is that I feel that installing rules
and procedures is a blatant slap in the face, saying that "you must follow
these rules because we don't trust you."

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:26 2006

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

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