Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jim Paris <jim@jtan.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	Guido Guenther <agx@sigxcpu.org>,
	linux-mips@oss.sgi.com
Subject: Re: ip22 watchdog timer
Date: Fri, 15 Feb 2002 15:33:05 -0500	[thread overview]
Message-ID: <20020215153305.A11087@neurosis.mit.edu> (raw)
In-Reply-To: <20020215152132.A602@dea.linux-mips.net>; from ralf@oss.sgi.com on Fri, Feb 15, 2002 at 03:21:32PM +0100

> >  BTW, why do people insist on sending patches as attachments -- it makes
> > commenting them helly twisted, sigh... 
> 
> How true.  MIME - broken solution for a broken design ;)  More serious,
> MIME makes sense when using a MUA that garbles patches like Netscape or
> certain versions of Pine.
> 
>   Ralf  (Prolly still be using Mutt + vi in 5 years ...)

Patches as attachments are actually really convenient with Mutt.
You can view them seperately, extract and save them easily, etc.

To comment on both the original message and the attachments: use
view-attachments (v), use tag-entry (t) on all of the parts you want
quoted in your reply, and then use tag-prefix & reply (;r) 
(or ;g or whatever).

But I digress :)

-jim

  parent reply	other threads:[~2002-02-15 21:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08 17:27 ip22 watchdog timer Guido Guenther
2002-02-15  4:56 ` Ralf Baechle
2002-02-15 12:06   ` Guido Guenther
2002-02-15 14:17     ` Maciej W. Rozycki
2002-02-15 14:21       ` Ralf Baechle
2002-02-15 14:41         ` Maciej W. Rozycki
2002-02-15 15:06           ` Ralf Baechle
2002-02-15 21:02             ` Matthew Dharm
2002-02-15 21:02               ` Matthew Dharm
2002-02-15 20:33         ` Jim Paris [this message]
2002-02-15 15:42       ` Guido Guenther
2002-02-15 16:19         ` Maciej W. Rozycki

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=20020215153305.A11087@neurosis.mit.edu \
    --to=jim@jtan.com \
    --cc=agx@sigxcpu.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    --cc=ralf@oss.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