From: Eli Zaretskii <eliz@is.elta.co.il>
To: todd whitesel <toddpw@windriver.com>
Cc: GDB Developers <gdb@sources.redhat.com>
Subject: Re: Two files with embedded control-M's
Date: Wed, 27 Nov 2002 22:06:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1021128080530.22888D-100000@is> (raw)
In-Reply-To: <200211280035.QAA21146@alabama.wrs.com>
On Wed, 27 Nov 2002, todd whitesel wrote:
> (How does one construct a patch in this case? Will email preserve CRLF's?)
I wouldn't trust mail agents on this one. I suggest sending the patch as
a binary attachment, perhaps uuencoded or in base64.
prev parent reply other threads:[~2002-11-28 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 16:35 todd whitesel
2002-11-27 22:06 ` Eli Zaretskii [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=Pine.SUN.3.91.1021128080530.22888D-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=toddpw@windriver.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