From: Eli Zaretskii <eliz@gnu.org>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: rmail and mime encoded patches annoyance
Date: Fri, 19 May 2023 13:51:15 +0300 [thread overview]
Message-ID: <83pm6wtx0c.fsf@gnu.org> (raw)
In-Reply-To: <E1pzuMh-0007DI-9Y@fencepost.gnu.org> (ams@gnu.org)
> From: "Alfred M. Szmidt" <ams@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Fri, 19 May 2023 03:17:27 -0400
>
> FWIW, I almost never use rmail-edit, and don't really understand why
> it's useful, let alone when a MIME patch is attached to it. If what
> you need is to edit the patch before applying it,
>
> It is more for commenting about the patch, in this case. One could
> start a new reply, but those aren't presitent, and sometimes patches
> take a week or two to go over.
I don't understand: if you reply with the attachment displayed (i.e.,
after you pres the "Show" button on the MIME attachment header line),
"C-c C-y" will yank the decoded attachment's text as well, and you can
then comment on it like you do with any other text of the original
message.
> Similar, I use this for longer responses, where I edit the message and
> add my reply/comments/... and then save the RMAIL buffer. And when
> you're done, you just reply with the notes you did.
I still don't understand why you need to use rmail-edit for that.
What's wrong with adding your reply/comments in the response message
after rmail-reply? If you want to save the response for editing or
replying later, there's FCC, or you can use BCC to send a copy to
yourself.
> then (a) that is not really recommended, since you will be applying
> code attributed to someone else with your own changes; and (b) you
> could always copy the patch to another buffer, edit it there, and
> then apply.
>
> Doing that multiple times a day gets old quick; was hoping to find a
> better way.
Like I say above: I don't understand why you'd need to do that even
once a day. I don't, and you can believe me that I review a lot of
patches sent as attachments, and not only for Emacs.
next prev parent reply other threads:[~2023-05-19 10:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 6:11 rmail and mime encoded patches annoyance Alfred M. Szmidt
2023-05-19 6:45 ` Eli Zaretskii
2023-05-19 7:17 ` Alfred M. Szmidt
2023-05-19 10:51 ` Eli Zaretskii [this message]
2023-05-19 11:08 ` Alfred M. Szmidt
2023-05-19 11:25 ` Eli Zaretskii
2023-05-19 11:31 ` Alfred M. Szmidt
2023-05-19 11:38 ` Eli Zaretskii
2023-05-19 11:39 ` Alfred M. Szmidt
2023-05-19 16:53 ` Bob Rogers
2023-05-21 0:46 ` Francesco Potortì
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=83pm6wtx0c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ams@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.