[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1238337530.2534.3.camel@ht.satnam>
Date: Sun, 29 Mar 2009 20:08:50 +0530
From: Jaswinder Singh Rajput <jaswinder@...nel.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Ingo Molnar <mingo@...e.hu>, Hugh Dickins <hugh@...itas.com>,
x86 maintainers <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git-pull -tip] x86: include inverse Xmas tree patches
On Sun, 2009-03-29 at 13:46 +0200, Thomas Gleixner wrote:
> On Sun, 29 Mar 2009, Jaswinder Singh Rajput wrote:
> > On Sun, 2009-03-29 at 00:40 +0100, Ingo Molnar wrote:
> > > * Hugh Dickins <hugh@...itas.com> wrote:
> > > >
> > > > Please find a better use for your time.
> > > >
> > > > Imagine, there might be developers out there with real work
> > > > to do in these files: all you are doing is throwing silly
> > > > little obstacles in their way.
> > >
> > > Actually, now is the right time to do such changes as we've just
> > > pushed all pending x86 changes upstream. And since these changes
> > > reduce the chance of future patch conflicts, they do help
> > > development. (in a small way)
> > >
> > > Nevertheless i'd suggest to make this a single commit, to not
> > > clobber the shortlog with it.
> > >
> >
> > I think individual patches will be better option, in case of unavoidable
> > situation we can simply revert that particular patch.
>
> What unavoidable situation ? That you broke stuff with your changes ?
> If you are so unsure about the quality of your changes, then the best
> option is to not pull that stuff at all.
>
OK. Tree deleted, thanks for your advice.
--
JSR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists