From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, Hugh Dickins <hugh@veritas.com>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git-pull -tip] x86: include inverse Xmas tree patches
Date: Sun, 29 Mar 2009 20:08:50 +0530 [thread overview]
Message-ID: <1238337530.2534.3.camel@ht.satnam> (raw)
In-Reply-To: <alpine.LFD.2.00.0903291345300.3397@localhost.localdomain>
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@veritas.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
next prev parent reply other threads:[~2009-03-29 14:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 14:48 Jaswinder Singh Rajput
2009-03-28 15:07 ` Joerg Roedel
2009-03-28 16:48 ` Jaswinder Singh Rajput
2009-03-28 17:16 ` Jaswinder Singh Rajput
2009-03-28 15:07 ` Alexey Dobriyan
2009-03-28 15:55 ` Alan Cox
2009-03-28 15:58 ` Alexey Dobriyan
2009-03-28 16:11 ` Jaswinder Singh Rajput
2009-03-28 16:28 ` Alan Cox
2009-03-28 19:03 ` Sam Ravnborg
2009-03-28 22:25 ` H. Peter Anvin
2009-03-28 22:37 ` Al Viro
2009-03-28 23:31 ` Thomas Gleixner
2009-03-28 23:34 ` Ingo Molnar
2009-03-28 23:39 ` Thomas Gleixner
2009-03-29 0:00 ` Ingo Molnar
2009-03-29 0:24 ` Al Viro
2009-03-29 10:25 ` Alexey Dobriyan
2009-03-29 0:28 ` Thomas Gleixner
2009-03-29 1:58 ` Ingo Molnar
2009-03-29 7:57 ` Jaswinder Singh Rajput
2009-03-28 15:17 ` Hugh Dickins
2009-03-28 23:40 ` Ingo Molnar
2009-03-29 6:38 ` Jaswinder Singh Rajput
2009-03-29 11:46 ` Thomas Gleixner
2009-03-29 14:38 ` Jaswinder Singh Rajput [this message]
2009-03-28 23:35 ` Ingo Molnar
2009-03-29 5:54 ` Jaswinder Singh Rajput
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1238337530.2534.3.camel@ht.satnam \
--to=jaswinder@kernel.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®