httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <>
Subject Re: Where to now
Date Sat, 10 Jan 1998 03:16:02 GMT
I'm sorry if it sounds that way, that's not it at all.  What bothers me is
the extra time I have to expend on each commit.  This means that I spend
less time doing small commits (i.e. small platform tweaks from the bugdb,
or small performance tweaks I see just as I'm reading the code) because
there's a threshold below which the effort spent preparing a
"presentation" of the patch here just isn't worth it. 

And on large commits the effort becomes wasted because folks have a hard
time grappling with a large commit and then it falls behind because other
commits sneak in before it, requiring extra effort to get it in.

It's only the mid size stuff that's reasonable... 

and I find this state deplorable. 


On Fri, 9 Jan 1998, Jim Jagielski wrote:

> Dean Gaudet wrote:
> > 
> > i.e. why should I be motivated to post a patch if I know
> > I can just commit the sucker in 48 hours anyway regardless of whether
> > someone reads it? 
> because, maybe, someone might have trouble with it? because, just maybe,
> it allows people to see what you are proposing?
> The only trouble I have with the commit-then-review is this attitude
> that I should be able to commit whatever the flark I want. That if
> I have to do any sort of effort to make people aware of what I'm
> doing, then forget it. This smells selfish.
> I'm not saying that this is how you feel, but that's how it
> _sounds_.
> -- 
> ====================================================================
>       Jim Jagielski            |       jaguNET Access Services
>           |
>             "Look at me! I'm wearing a cardboard belt!"

View raw message