httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <>
Subject Re: Where to now
Date Fri, 09 Jan 1998 23:22:33 GMT
Brian Behlendorf wrote:
> Just to explore this further; what's the threat if code is reviewed after
> it's committed?  So long as those with commit access agree to a set of
> principles (as I started with yesterday, I haven't read all my messages yet
> to see if there's been responses), I don't see the problem.  I do see
> something we could add to those principles - there should never be an
> argument to the extent of "well it's already committed, so there's nothing
> that can be done about it".  We should not be afraid to make mistakes, and
> roll back patches or fix code in the tree if one was made.

There is little to no "threat" if there are clear guidelines.
At the least, I think some sort of notice that says "Hey, I'm
working on this idea" would be good.

      Jim Jagielski            |       jaguNET Access Services           |
            "Look at me! I'm wearing a cardboard belt!"

View raw message