From: Ronald Bultje <rbultje@ronald.bitfreak.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] 2.6.0-test4: small updates for zoran driver
Date: 24 Aug 2003 06:33:16 +0200 [thread overview]
Message-ID: <1061699596.4304.257.camel@localhost.localdomain> (raw)
In-Reply-To: <20030823202946.09625532.akpm@osdl.org>
Hey Andrew,
On Sun, 2003-08-24 at 05:29, Andrew Morton wrote:
> I would have done it anyway, but half the URLs you provided go 404.
[..]
> > Is anyone else here using
> > Evolution to send in patches or is Evolution broken?
>
> It's broken. So is mozilla mailnews.
>
> Attachments should be OK. One patch per email, with a good title and the
> changelog text in the email body. Nice and easy.
Ok, I'll use attachments from now on. Do you want me to re-submit the
patches?
Thanks,
Ronald
--
Ronald Bultje <rbultje@ronald.bitfreak.net>
prev parent reply other threads:[~2003-08-24 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-24 0:13 [PATCH] 2.6.0-test4: small updates for zoran driver Ronald Bultje
2003-08-24 3:29 ` Andrew Morton
2003-08-24 4:33 ` Ronald Bultje [this message]
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=1061699596.4304.257.camel@localhost.localdomain \
--to=rbultje@ronald.bitfreak.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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).