From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 1/2] Cleaning up modedb file
Date: Tue, 11 Jan 2011 13:01:15 +0000 [thread overview]
Message-ID: <20110111130115.GC774@linux-sh.org> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB03232B6B12@dbde02.ent.ti.com>
On Tue, Jan 11, 2011 at 06:30:27PM +0530, Janorkar, Mayuresh wrote:
> Hi Paul,
>
> The patch which I received was having tabs not spaces.
>
> I have seen some archives in which patches can also sent as an email attachment.
>
> Can send this patch as an attachment?
> (This particular being a special case.)
>
Yes, if you can't do much about your corporate mailer mangling patches
then an attachment is of course fine. Patchwork is generally smart enough
to figure these things out, anyways.
next prev parent reply other threads:[~2011-01-11 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 11:13 [PATCH 1/2] Cleaning up modedb file Janorkar, Mayuresh
2011-01-06 6:55 ` Paul Mundt
2011-01-11 13:01 ` Paul Mundt [this message]
2011-01-11 13:12 ` Janorkar, Mayuresh
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=20110111130115.GC774@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-fbdev@vger.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;
as well as URLs for NNTP newsgroup(s).