From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: gingold@adacore.com, mark.kettenis@xs4all.nl, gdb-patches@sourceware.org
Subject: Re: [RFA] Darwin: single step through sigreturn
Date: Mon, 08 Dec 2008 18:14:00 -0000 [thread overview]
Message-ID: <200812081813.mB8IDKrf016619@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20081208174805.GF3823@adacore.com> (message from Joel Brobecker on Mon, 8 Dec 2008 18:48:05 +0100)
> Date: Mon, 8 Dec 2008 18:48:05 +0100
> From: Joel Brobecker <brobecker@adacore.com>
>
> > Argh, copy and cut issues. Is it ok to attach the patches ?
>
> Absolutely!
Not really. Some MIME implementations do horrible things to diffs.
I'm probably fighting a losing battle here, but the preferred way to
send diffs is inline, using a sane mail client that doesn't add any
formatting of its own.
next prev parent reply other threads:[~2008-12-08 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 15:29 Tristan Gingold
2008-12-04 22:29 ` Mark Kettenis
2008-12-05 11:10 ` Tristan Gingold
2008-12-08 17:48 ` Joel Brobecker
2008-12-08 18:14 ` Mark Kettenis [this message]
2008-12-08 19:06 ` Joel Brobecker
2008-12-08 19:22 ` Daniel Jacobowitz
2008-12-08 20:44 ` Joel Brobecker
2008-12-08 20:53 ` Mark Kettenis
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=200812081813.mB8IDKrf016619@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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