From: "Štěpán Němec" <stepnem@gmail.com>
To: Yuan Fu <casouri@gmail.com>
Cc: 39181@debbugs.gnu.org
Subject: bug#39181: 27.0.50; [PATCH] Allow users to store & restore gdb-mi layout
Date: Fri, 13 Mar 2020 23:12:42 +0100 [thread overview]
Message-ID: <87d09foqed.fsf@gmail.com> (raw)
In-Reply-To: <DCEE0C58-CF4C-4546-8AA2-6E89766E23BE@gmail.com>
On Fri, 13 Mar 2020 17:40:30 -0400
Yuan Fu wrote:
> I added some comments in the menu-map code. Hope that’s helps.
Thanks.
> All fixed.
Confirmed, thank you.
>> P.S.: This time your patch somehow ended up hidden as
>> application/ocet-stream after the HTML part, instead of inline in plain
>> text.
> I’m not sure what causes that. I’ve been using Apple Mail and I just
> copy the patch file into my reply. It actually surprises me that they
> showed up in plain text before. This time I made the mail plain text,
> hopefully that makes the patch also in plain text.
Yeah, actually the difference wasn't in the patch MIME type per se, but
in the fact that it was included in a multipart/mixed section together
with the HTML part (all that in one big multipart/alternative), so it
wasn't visible in the text/plain part. This one is same as your previous
e-mails again (text/plain), thanks.
--
Štěpán
next prev parent reply other threads:[~2020-03-13 22:12 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5e950f28.1c69fb81.61726.5731.GMR@mx.google.com>
2020-01-18 20:57 ` bug#39181: 27.0.50; [PATCH] Allow users to store & restore gdb-mi layout Yuan Fu
2020-01-31 10:13 ` Eli Zaretskii
2020-02-02 14:22 ` Yuan Fu
2020-02-07 22:28 ` Yuan Fu
2020-02-10 4:56 ` Yuan Fu
2020-02-15 8:08 ` Eli Zaretskii
2020-02-15 9:55 ` martin rudalics
2020-02-15 10:19 ` Eli Zaretskii
2020-02-15 20:37 ` Yuan Fu
2020-02-16 10:00 ` martin rudalics
2020-03-03 23:41 ` Yuan Fu
2020-03-04 13:28 ` Fu Yuan
2020-03-05 6:12 ` Yuan Fu
2020-03-05 9:14 ` martin rudalics
2020-03-07 18:09 ` Yuan Fu
2020-03-07 19:07 ` Štěpán Němec
2020-03-07 19:17 ` Yuan Fu
2020-03-09 9:01 ` martin rudalics
2020-03-09 17:59 ` Yuan Fu
2020-03-09 19:18 ` Štěpán Němec
2020-03-09 20:17 ` Yuan Fu
2020-03-09 20:54 ` Štěpán Němec
2020-03-10 8:49 ` martin rudalics
2020-03-10 18:05 ` Fu Yuan
2020-03-11 8:52 ` martin rudalics
2020-03-11 9:26 ` Štěpán Němec
2020-03-12 8:22 ` martin rudalics
2020-03-12 8:49 ` Štěpán Němec
2020-03-12 19:21 ` Yuan Fu
2020-03-13 20:09 ` Yuan Fu
[not found] ` <87lfo4netg.fsf@gmail.com>
2020-03-13 21:13 ` Štěpán Němec
2020-03-13 21:40 ` Yuan Fu
2020-03-13 22:12 ` Štěpán Němec [this message]
2020-03-15 15:55 ` martin rudalics
2020-03-16 0:13 ` Yuan Fu
2020-03-16 9:24 ` martin rudalics
2020-03-20 20:03 ` Yuan Fu
2020-03-20 20:58 ` Štěpán Němec
2020-03-21 18:00 ` Yuan Fu
2020-03-21 18:39 ` Štěpán Němec
2020-03-21 21:03 ` Yuan Fu
2020-03-21 21:49 ` Štěpán Němec
2020-03-24 16:14 ` Yuan Fu
2020-03-27 9:01 ` martin rudalics
2020-03-27 16:28 ` Yuan Fu
2020-04-14 8:05 ` martin rudalics
2020-03-10 8:48 ` martin rudalics
2020-04-14 1:17 ` bug#39181: Fwd: Delivery Status Notification (Failure) Yuan Fu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d09foqed.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=39181@debbugs.gnu.org \
--cc=casouri@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).