From: Ralf Baechle <ralf@linux-mips.org>
To: Jon Burgess <Jon_Burgess@eur.3com.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Problem running Mips2 user space code
Date: Fri, 20 Sep 2002 02:47:12 +0200 [thread overview]
Message-ID: <20020920024712.A27442@linux-mips.org> (raw)
In-Reply-To: <80256C39.0056AAAC.00@notesmta.eur.3com.com>; from Jon_Burgess@eur.3com.com on Thu, Sep 19, 2002 at 04:40:05PM +0100
On Thu, Sep 19, 2002 at 04:40:05PM +0100, Jon Burgess wrote:
> in case it is caused by a toolchain problem. I just read Ralfs comment
> about not sending files, tars or compressed files to the mailing list,
> hopefully he won't mind the source.
The comment was refering to patches sent to me. Having to unzip and untar
patch sets is just a waste of time. The easiest thing to deal with my is
one inline patch per email, no attachments. For those pour souls that use
mails that garble patches (Some Pine versions, Netscape, Mozilla, Lotus
Notes, MS stuff) one patch attached per mail.
Ralf
next prev parent reply other threads:[~2002-09-20 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 15:40 Problem running Mips2 user space code Jon Burgess
2002-09-20 0:47 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-19 16:41 Jon Burgess
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=20020920024712.A27442@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Jon_Burgess@eur.3com.com \
--cc=linux-mips@linux-mips.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