From: Andrew Morton <akpm@osdl.org>
To: "Luke Yang" <luke.adi@gmail.com>
Cc: pj@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix bug: flat binary loader doesn't check fd table full
Date: Sat, 25 Mar 2006 13:06:57 -0800 [thread overview]
Message-ID: <20060325130657.18dcf4e2.akpm@osdl.org> (raw)
In-Reply-To: <489ecd0c0603250726l118f622asb77d244ef8c0c129@mail.gmail.com>
"Luke Yang" <luke.adi@gmail.com> wrote:
>
> On 3/25/06, Paul Jackson <pj@sgi.com> wrote:
> > > > Anyone knows how to avoid "tab to space" converting in gmail?
> > >
> > > If I knew, I'd put it in my .signature :(
> >
> > If you use sendpatchset:
> >
> > http://www.speakeasy.org/~pj99/sgi/sendpatchset
> >
> > with the gmail SMTP server "smtp.gmail.com" you can send patches from
> > your gmail account without tab destruction.
> >
> > The documentation for sendpatchset is within the script. Grep for
> > 'gmail' in the script to see where to hack in your gmail account and
> > password (low tech configuration ;)
> Thank you for your help. But my problem is that I can only access 80
> and 443 ports behind the company firewall :(. So I guess that doesn't
> work for me.
>
> For now I'll put the patch both in the mail text and as the
> attachment, so maintainers can use the attached right-formatted patch
> and other can also reply my patch in the text. Andrew, is it
> acceptable?
hm, yes I suppose that's OK.
> Any google guy here?
Plenty. Seems that half the people I've ever met are now working for
google.
> Please, add this feature in gmail...
I wouldn't call "stop corrupting message bodies" a feature request.
Would be nice.
next prev parent reply other threads:[~2006-03-25 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 7:10 [PATCH] Fix bug: flat binary loader doesn't check fd table full Luke Yang
2006-03-23 7:46 ` Andrew Morton
[not found] ` <489ecd0c0603230115h4dd2b16fg54cfd97739a8b339@mail.gmail.com>
2006-03-23 9:17 ` Andrew Morton
2006-03-25 4:53 ` Paul Jackson
2006-03-25 15:26 ` Luke Yang
2006-03-25 21:06 ` Andrew Morton [this message]
[not found] <5Tsh4-2q0-13@gated-at.bofh.it>
[not found] ` <5TsTM-3aB-1@gated-at.bofh.it>
[not found] ` <5Tuj1-5lw-31@gated-at.bofh.it>
[not found] ` <5Tuj1-5lw-29@gated-at.bofh.it>
[not found] ` <5U92I-6ki-11@gated-at.bofh.it>
[not found] ` <5UiSm-3FG-17@gated-at.bofh.it>
2006-03-26 11:34 ` Bodo Eggert
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=20060325130657.18dcf4e2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.adi@gmail.com \
--cc=pj@sgi.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