all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 66450@debbugs.gnu.org, Bruno Victal <mirai@makinata.eu>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#66450: 29.1; Debbugs/Gnus sometimes corrupt git formatted patches
Date: Sat, 14 Oct 2023 09:40:58 -0700	[thread overview]
Message-ID: <87wmvpcg2t.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87fs2dnu5g.fsf@gmx.de> (Michael Albinus's message of "Sat, 14 Oct 2023 16:41:31 +0200")

Michael Albinus <michael.albinus@gmx.de> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
> Hi Eric,
>
>> Gnus is the obvious choice for scanning incoming bug reports and seeing
>> if any have to do with me (very few of them do!). But Debbugs is the
>> natural choice for keeping track of bugs once I do decide to work on
>> them. Getting from Gnus to Debbugs isn't a no-brainer -- I once wrote a
>> command that adds the bug number of the article under point to
>> `debbugs-gnu-tagged', to be called on articles in the
>> "nntp:gmane.emacs.bugs" group, but I never managed to form the habit of
>> using it.
>
> I use a different approach. I have taught Gnus to follow bug references
> in Summary and Article buffers. The relevant setting is
>
> (setq bug-reference-url-format "https://debbugs.gnu.org/%s")
> (add-hook 'bug-reference-mode-hook 'debbugs-browse-mode)
> (add-hook 'bug-reference-prog-mode-hook 'debbugs-browse-mode)
>
> (add-hook 'gnus-summary-mode-hook 'bug-reference-mode)
> (add-hook 'gnus-article-mode-hook 'bug-reference-mode)
>
> Then, bug references are highlighted, and I can select them with the mouse.
>
>> Anyway, this bug report isn't the place for the discussion!
>
> Indeed. But there's no proper place for discussion, and the Debbugs User
> Guide, which explains this, isn't read by anybody. See
> (info "(debbugs-ug) Minor Mode")
>
> So I spread The Truth™ wherever I can :-)

The Truth has been heard! I can't believe I didn't know about all this
earlier. I may even work on more bugs now!

Thanks,
Eric





  reply	other threads:[~2023-10-14 16:40 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wmvpcg2t.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=66450@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --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 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.