unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 66450@debbugs.gnu.org, Bruno Victal <mirai@makinata.eu>,
	Michael Albinus <michael.albinus@gmx.de>
Subject: bug#66450: 29.1; Debbugs/Gnus sometimes corrupt git formatted patches
Date: Tue, 17 Oct 2023 11:19:18 -0400	[thread overview]
Message-ID: <8734y9uvih.fsf@gmail.com> (raw)
In-Reply-To: <877cnlcphm.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 17 Oct 2023 07:06:45 -0700")

Hi Eric,

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> On 10/17/23 09:03 AM, Michael Albinus wrote:
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>>
>>> Hello,
>>
>> Hi Maxim,
>>
>>> Something similar to this have been recently added to the Guix
>>> "Contributing" section, see
>>> <https://guix.gnu.org/en/manual/devel/en/html_node/The-Perfect-Setup.html#Viewing-Bugs-within-Emacs>
>>> or info "(guix) The Perfect Setup".  The regexps have been turned into
>>> 'rx' expressions for readability.
>>
>> Thanks for the information. Scrolling through this guide, maybe I can
>> give you some further comments? In
>> <https://guix.gnu.org/en/manual/devel/en/html_node/Debbugs-User-Interfaces.html>,
>> you recommend the command 'C-u M-x debbugs-gnu RET RET guix-patches RET
>> n y'. However, if you configure debbugs-gnu-default-packages to '("guix"
>> "guix-patches"), you don't need the prefix argument. Furthermore, Guix
>> has its own commands in Debbugs, like debbugs-gnu-guix-search.
>>
>> All of this is off-topic for this bug. But I thought it might be helpful.
>
> Speaking of which... Unless someone wants to make an argument about
> changing the defaults of the pipe-article command, it might be time to
> close this report. Though it has been unusually productive!

If we worry about backward compatibility, perhaps we could add a
defcustom variable that'd be named
e.g. 'gnus-always-process-raw-message' or similar, that'd do what its
name says (e.g. when using 'pipe' or save-article, it'd process the raw
message).  Eventually, it could be made the default behavior, if it has
enough support.

I could try implementing that, if it seems a good idea?

-- 
Thanks,
Maxim





  reply	other threads:[~2023-10-17 15:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 18:29 bug#66450: 29.1; Debbugs/Gnus sometimes corrupt git formatted patches Maxim Cournoyer
2023-10-11 20:37 ` Eric Abrahamsen
2023-10-14 15:22   ` Maxim Cournoyer
2023-10-14 15:35     ` Maxim Cournoyer
2023-10-14 16:43     ` Eric Abrahamsen
2023-10-12 16:52 ` Michael Albinus
2023-10-12 22:04   ` Eric Abrahamsen
2023-10-13  7:01     ` Michael Albinus
2023-10-13 16:53       ` Eric Abrahamsen
2023-10-14 14:41         ` Michael Albinus
2023-10-14 16:40           ` Eric Abrahamsen
2023-10-16 14:59           ` Maxim Cournoyer
2023-10-17  7:03             ` Michael Albinus
2023-10-17 14:06               ` Eric Abrahamsen
2023-10-17 15:19                 ` Maxim Cournoyer [this message]
2023-10-17 16:41                   ` Eric Abrahamsen
2023-10-18 18:50                     ` Maxim Cournoyer
2023-10-18 19:40                       ` Eric Abrahamsen
2023-10-19  1:01                         ` Maxim Cournoyer
2023-10-19  2:50                           ` Eric Abrahamsen
2023-10-19  3:38                             ` Maxim Cournoyer
2023-10-19  6:26                         ` Visuwesh
2024-03-10 15:12                         ` Eric Abrahamsen
2023-10-19  1:53               ` Maxim Cournoyer
2023-10-19  7:05                 ` Michael Albinus
2023-10-14 20:27         ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]         ` <875y390x1s.fsf@>
2023-10-15  1:13           ` 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=8734y9uvih.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=66450@debbugs.gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=michael.albinus@gmx.de \
    --cc=mirai@makinata.eu \
    /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).