Not actually sending patches (was: [patch, fortran] [4.6 Regression] PR47853 Inquire affected by previous read)

[Jakub Jelinek]

On Tue, Feb 08, 2011 at 11:07:06PM -0800, Steve Kargl wrote:
> On Wed, Feb 09, 2011 at 07:26:04AM +0100, Ralf Wildenhues wrote:
> > Your mail does not contain the actual change that you applied.
> > It looks like this is becoming a trend, and I think it needs to stop.
> > 
> > The gcc-patches mailing list is read by an estimated 300+ people.  Most
> > of them have very little time, but many of them are quickly able to
> > point out that missing set of parentheses, that typo, or that unportable
> > construct you may have used in your inline posted patch.  Not reading a
> > patch that doesn't interest them maybe costs them three seconds.
> > 
> > But going to SVN or git, or just gcc-cvs, and digging out the revision
> > number just to read the patch, much less comment on it, easily takes
> > more than a minute.  That means, most readers won't do it, unless the
> > patch happens to really really interest them.
> > 
> > So please, save 300 people work by investing 10 seconds yourself and
> > post the actual patch.  In turn you get something out too: better
> > review.
> > 
> 
> I think your email is a tad bit over the top here.  Yes,
> there are 300+ people who read gcc-patches, and there
> will be 299+ people who see a Fortran patch and simply 
> delete it.

I agree with Ralf, gcc-patches should be for patches and their review,
the mails with svn ci output are just noise, something that can be seen from
svn or on gcc-cvs mailing list.

	Jakub