mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Pranith Kumar <pranith.hacks@gmail.com>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL][PATCH 1/1] Fix warning in staging/otus/ioctl.c
Date: Thu, 4 Jun 2009 20:37:10 +0200	[thread overview]
Message-ID: <ca2dc2820906041137m2075ae1bye03c08fc1b5c0368@mail.gmail.com> (raw)
In-Reply-To: <4A27616C.6030802@gmail.com>

On Thu, Jun 4, 2009 at 7:53 AM, Pranith Kumar <pranith.hacks@gmail.com> wrote:
> Greg KH wrote:
>>
>> On Wed, Jun 03, 2009 at 12:19:26PM +0530, Pranith Kumar wrote:
>>
>>>
>>> I am using Gmail, which does this. I haven't figured out how to
>>> configure this thing yet.
>>>
>>
>> Please try reading Documentation/email-clients.txt and try again.
>>
>>
>
> Ok, I've configured my email client now. Resubmitting patch.
>

Here is a tip: Submit the patch to yourself first, then use the
GMail's option "See original" and check if your patch is linewrapped.
After being sure that your patch is not linewrapped, send it to LKML.

That is what I did while finding a decent email client : )

PS: Do not forget to repeat the process every time you configure a new
email client!

  parent reply	other threads:[~2009-06-04 18:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29  7:54 Pranith Kumar
2009-06-02 21:47 ` Greg KH
2009-06-03  6:49   ` Pranith Kumar
2009-06-03 15:21     ` Greg KH
2009-06-04  5:53       ` Pranith Kumar
2009-06-04 17:56         ` Greg KH
2009-06-05  5:10           ` Pranith Kumar
2009-06-05  6:15             ` Pranith Kumar
2009-06-04 18:37         ` Miguel Ojeda [this message]
2009-06-08  7:19 Pranith Kumar
2009-06-08  8:08 ` Pranith Kumar
2009-06-08  9:09   ` Stefan Richter
2009-06-08 10:02     ` Pranith Kumar
2009-06-08 18:01       ` Stefan Richter
2009-06-08 18:18         ` Stefan Richter

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=ca2dc2820906041137m2075ae1bye03c08fc1b5c0368@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pranith.hacks@gmail.com \
    /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®