From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael.albinus@gmx.de, 69017@debbugs.gnu.org
Subject: bug#69017: 30.0.50; [debbugs] Make compilation step optional in debbugs-gnu-apply-patch
Date: Sat, 10 Feb 2024 11:58:56 -0800 [thread overview]
Message-ID: <87eddkxf9b.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86bk8ot8zx.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 10 Feb 2024 21:27:46 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: 69017@debbugs.gnu.org
>> From: Eric Abrahamsen <eric@ericabrahamsen.net>
>> Date: Sat, 10 Feb 2024 11:23:30 -0800
>>
>> Out of curiosity, do you use any convenience functions for applying
>> patches from email->repository?
>
> I use M-|, FWIW.
That's what I was trying to avoid! You're the one who has to handle
attachments vs inline, type out the directory location, decide between
"git am" and "git apply", etc...
If you're doing it 50 times a day, maybe the muscle memory (or command
history) means it's not a big deal.
next prev parent reply other threads:[~2024-02-10 19:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 17:42 bug#69017: 30.0.50; [debbugs] Make compilation step optional in debbugs-gnu-apply-patch Eric Abrahamsen
2024-02-10 18:54 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-10 19:23 ` Eric Abrahamsen
2024-02-10 19:27 ` Eli Zaretskii
2024-02-10 19:58 ` Eric Abrahamsen [this message]
2024-02-10 20:26 ` Eli Zaretskii
2024-02-10 20:52 ` Eric Abrahamsen
2024-02-11 8:18 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-11 15:05 ` Eric Abrahamsen
2024-02-11 15:43 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-16 5:50 ` Eric Abrahamsen
2024-02-11 8:11 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-11 15:05 ` Eric Abrahamsen
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=87eddkxf9b.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=69017@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
/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).