All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Pavel Fedin <sonic.amiga@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/9] Amiga SmartFileSystem
Date: Mon, 9 Feb 2009 01:36:19 -0700	[thread overview]
Message-ID: <20090209083619.GL31509@parisc-linux.org> (raw)
In-Reply-To: <187c6cc60902082253s20707281s38b7dc76abcde92b@mail.gmail.com>

On Mon, Feb 09, 2009 at 09:53:25AM +0300, Pavel Fedin wrote:
> diff -ruN linux-source-2.6.24.orig/Documentation/filesystems/00-INDEX
> linux-source-2.6.24/Documentation/filesystems/00-INDEX

This patch is corrupted ;-(  From Documentation/email-clients.txt:

Gmail (Web GUI)

If you just have to use Gmail to send patches, it CAN be made to work.  It
requires a bit of external help, though.

The first problem is that Gmail converts tabs to spaces.  This will
totally break your patches.  To prevent this, you have to use a different
editor.  There is a firefox extension called "ViewSourceWith"
(https://addons.mozilla.org/en-US/firefox/addon/394) which allows you to
edit any text box in the editor of your choice.  Configure it to launch
your favorite editor.  When you want to send a patch, use this technique.
Once you have crafted your messsage + patch, save and exit the editor,
which should reload the Gmail edit box.  GMAIL WILL PRESERVE THE TABS.
Hoorah.  Apparently you can cut-n-paste literal tabs, but Gmail will
convert those to spaces upon sending!

The second problem is that Gmail converts tabs to spaces on replies.  If
you reply to a patch, don't expect to be able to apply it as a patch.

The last problem is that Gmail will base64-encode any message that has a
non-ASCII character.  That includes things like European names.  Be
aware.

Gmail is not convenient for lkml patches, but CAN be made to work.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2009-02-09  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09  6:53 [PATCH 1/9] Amiga SmartFileSystem Pavel Fedin
2009-02-09  8:36 ` Matthew Wilcox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-26 12:08 Pavel Fedin

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=20090209083619.GL31509@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sonic.amiga@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.