From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: Kris Warkentin <kewarken@qnx.com>, gdb-patches@sources.redhat.com
Subject: Re: Add Kris Warkentin to write after maintainers.
Date: Mon, 24 Feb 2003 20:01:00 -0000 [thread overview]
Message-ID: <3E5A7AB2.2010005@redhat.com> (raw)
In-Reply-To: <ro1heat1q0t.fsf@jackfruit.Stanford.EDU>
> For what it's worth, the mailer that I use (GNUS) seems to think that
> text/x-patch is the appropriate MIME type for patches. Certainly I
> agree that application/octet-stream is a bad idea, and frankly I think
> just inserting patches into the buffer instead of attaching them is
> easiest. But there's a case to be made for attaching patches instead;
> if so, I think text/x-patch is the way to go. Hopefully, in that
> case, any mailer will notice the text/ part and will be willing to
> display the contents without too much coercion.
Looks good in theory, I've seen problems with unknown types.
Anyway, Kris has found that .txt works!
Andrew
next prev parent reply other threads:[~2003-02-24 20:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 22:25 patch to allow target defined solib search method Kris Warkentin
2003-02-22 2:04 ` Kevin Buettner
2003-02-22 4:33 ` Kris Warkentin
2003-02-22 6:14 ` Daniel Jacobowitz
2003-02-24 16:04 ` Kris Warkentin
[not found] ` <1030222021025.ZM18868@localhost.localdomain>
[not found] ` <003301c2da28$71ce7ce0$2a00a8c0@dash>
[not found] ` <3E5A4ABD.1080706@redhat.com>
2003-02-24 16:53 ` Add Kris Warkentin to write after maintainers Kris Warkentin
2003-02-24 17:11 ` Andrew Cagney
2003-02-24 17:16 ` Kris Warkentin
2003-02-24 18:00 ` Kris Warkentin
2003-02-24 18:10 ` Andrew Cagney
2003-02-24 18:40 ` David Carlton
2003-02-24 20:01 ` Andrew Cagney [this message]
2003-02-24 20:12 ` Kris Warkentin
2003-02-24 18:50 ` Daniel Jacobowitz
2003-02-24 20:04 ` Andrew Cagney
2003-02-24 20:18 ` Daniel Jacobowitz
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=3E5A7AB2.2010005@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=gdb-patches@sources.redhat.com \
--cc=kewarken@qnx.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