[Intel-gfx] [PATCH] Typo.

Jesse Barnes jbarnes at virtuousgeek.org
Thu Jun 11 21:31:59 CEST 2009


On Thu, 11 Jun 2009 08:32:46 +0200
Paul Menzel <paulepanter at users.sourceforge.net> wrote:

> Am Dienstag, den 09.06.2009, 15:23 -0700 schrieb Jesse Barnes:
> > On Sun, 31 May 2009 20:38:10 +0200
> > Paul Menzel <paulepanter at users.sourceforge.net> wrote:
> > 
> > > Signed-off-by: Paul Menzel <paulepanter at users.sourceforge.net>
> > > ---
> > >  RELEASING |    2 +-
> > >  1 files changed, 1 insertions(+), 1 deletions(-)
> > > 
> > > diff --git a/RELEASING b/RELEASING
> > > index 2196c8f..e32ecf6 100644
> > > --- a/RELEASING
> > > +++ b/RELEASING
> > > @@ -37,7 +37,7 @@ The process for releasing a new tarball is as
> > > follows: 
> > >  	At the very least, add the release notes from the NEWS
> > > file. 
> > > -	The message is generated as
> > > xf86-video-inte-<version>.announce
> > > +	The message is generated as
> > > xf86-video-intel-<version>.announce 
> > >  	For snapshots and release candidates, mail to:
> > >  
> > 
> > A note on these sorts of cleanups:  I think they're a good idea in
> > general, but only if they're done as part of some other, real
> > work.  I want to avoid us getting into a kernel janitors type
> > situation where we get a bunch of trivial patches w/o real changes,
> > just adding noise to the mailing list and commit logs.
> > 
> > So please, by all means, contribute patches to fix issues you find
> > and feel free to clean stuff up in those areas at the same time,
> > but don't fall into the trap of just scrubbing the driver of
> > spelling errors. It's a siren song that's affected far too many as
> > it is! :)
> 
> Sorry for this. I thought it is better style to submit whitespace or
> typo patches separately so that the other patches can be reviewed
> easier and if the other fix does not get accepted at least this
> trivial stuff does not get lost.

Oh yes they should definitely be separate patches; just included in a
series working on that area.  I realized I didn't make that clear when
I sent this out.  Anyway; future fixes + cleanups are definitely
welcome!

-- 
Jesse Barnes, Intel Open Source Technology Center



More information about the Intel-gfx mailing list