From: Paul Jackson <pj@sgi.com>
To: "David S. Miller" <davem@redhat.com>
Cc: pat@computer-refuge.org, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org, brylow@cs.purdue.edu
Subject: Re: [PATCH] Re: BUG: 2.6.6-rc3 on SMP/SPARC64 (Sun E3000)?
Date: Thu, 20 May 2004 09:30:04 +0000 [thread overview]
Message-ID: <20040520023004.3c7e2446.pj@sgi.com> (raw)
In-Reply-To: <20040519210844.26337af4.davem@redhat.com>
> since your email client changed all the tabs into spaces.
Might not have been his email client. Another easy way to botch the
tabs is to cut+paste the patch into the email's message composition
window, for those using gui-style mailers, such as Kmail (Patrick) or
Sylpheed (myself). One can still inline patches with such tools - one
just has to be careful to read them into (File:Insert, perhaps) the
outgoing message from a file, rather than via cut+paste.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
WARNING: multiple messages have this Message-ID (diff)
From: Paul Jackson <pj@sgi.com>
To: "David S. Miller" <davem@redhat.com>
Cc: pat@computer-refuge.org, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org, brylow@cs.purdue.edu
Subject: Re: [PATCH] Re: BUG: 2.6.6-rc3 on SMP/SPARC64 (Sun E3000)?
Date: Thu, 20 May 2004 02:30:04 -0700 [thread overview]
Message-ID: <20040520023004.3c7e2446.pj@sgi.com> (raw)
In-Reply-To: <20040519210844.26337af4.davem@redhat.com>
> since your email client changed all the tabs into spaces.
Might not have been his email client. Another easy way to botch the
tabs is to cut+paste the patch into the email's message composition
window, for those using gui-style mailers, such as Kmail (Patrick) or
Sylpheed (myself). One can still inline patches with such tools - one
just has to be careful to read them into (File:Insert, perhaps) the
outgoing message from a file, rather than via cut+paste.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-05-20 9:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 15:49 BUG: 2.6.6-rc3 on SMP/SPARC64 (Sun E3000)? & MD Patrick Finnegan
2004-05-08 22:35 ` BUG: 2.6.6-rc3 on SMP/SPARC64 (Sun E3000) & MD / ksymoops output Patrick Finnegan
2004-05-08 22:35 ` Patrick Finnegan
2004-05-12 0:57 ` [PATCH] Re: BUG: 2.6.6-rc3 on SMP/SPARC64 (Sun E3000)? Patrick Finnegan
2004-05-12 0:57 ` Patrick Finnegan
2004-05-20 4:08 ` David S. Miller
2004-05-20 4:08 ` David S. Miller
2004-05-20 9:30 ` Paul Jackson [this message]
2004-05-20 9:30 ` Paul Jackson
2004-05-20 15:44 ` Pete Zaitcev
2004-05-20 15:44 ` Pete Zaitcev
2004-05-20 17:00 ` Paul Jackson
2004-05-20 17:00 ` Paul Jackson
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=20040520023004.3c7e2446.pj@sgi.com \
--to=pj@sgi.com \
--cc=brylow@cs.purdue.edu \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pat@computer-refuge.org \
--cc=sparclinux@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 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.