From: Ingo Molnar <mingo@elte.hu>
To: Kevin Diggs <kevdig@hypersurf.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-kernel@vger.kernel.org, david@fromorbit.com, arnd@arndb.de,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: {NOT a PATCH} Corrections please ...
Date: Fri, 22 Aug 2008 09:02:49 +0200 [thread overview]
Message-ID: <20080822070249.GW14110@elte.hu> (raw)
In-Reply-To: <48ADC65F.6000705@hypersurf.com>
* Kevin Diggs <kevdig@hypersurf.com> wrote:
> Ingo Molnar wrote:
>> * Kevin Diggs <kevdig@hypersurf.com> wrote:
>>
>>
>>> Here is the latest (maybe line wrap is set to 99 so it won't be
>>> goofed anymore?):
>>
>>
>> the patch wont apply as it has whitespace corruption (double spaces).
>> Please check Documentation/email-clients.txt.
>>
>> Ingo
>>
>>
> The double spacing between the diffs? That will prevent it from
> applying?
No. It's a per line corruption. Instead of:
"+<space>code"
your mail had:
"+<space><space>code"
i usually fix that up for small patch but this wasnt a smaller patch :)
> Who should this patch be sent to when it is ready? Also, I think I
> remember reading in submitting patches that patches should be cced to
> the general linux-kernel list. This correct?
me would be fine, it's scheduler code. I can take MIME attachments too
if that's easier for you.
Ingo
prev parent reply other threads:[~2008-08-22 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 1:30 Kevin Diggs
2008-08-20 1:52 ` Dave Chinner
2008-08-20 9:59 ` Ingo Molnar
2008-08-20 10:57 ` Stefan Richter
2008-08-20 19:59 ` Kevin Diggs
2008-08-21 10:30 ` Ingo Molnar
2008-08-21 19:47 ` Kevin Diggs
2008-08-22 7:02 ` Ingo Molnar [this message]
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=20080822070249.GW14110@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=arnd@arndb.de \
--cc=david@fromorbit.com \
--cc=kevdig@hypersurf.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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®