Gnus development mailing list
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Gnus bugfixing is broken.
Date: Mon, 14 Mar 2011 16:17:55 +0100	[thread overview]
Message-ID: <87hbb5ivdo.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m3oc5d3gju.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 14 Mar 2011 15:47:17 +0100")

[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> David Kastrup <dak@gnu.org> writes:
>
>> It does not appear like the bug channel fed directly by the gnus-bug
>> command is actually being read by anybody.
>
> I read it daily.  But I've been busy, so I haven't responded to anything
> for a week.
>
>> It has now been about two weeks that message-yank-original has stopped
>> being functional for installations that don't have cl loaded permanently
>> (namely standard Emacs installations).
>
> You reported it
>
> Date: Tue, 08 Mar 2011 15:26:17 +0100 (6 days, 19 minutes, 18 seconds ago)

"stopped being functional" is not the same as "you reported it".  Sure,
I reported it about a week ago.  It has been several days before that
that it appeared in the upstream git archive of Emacs.  It presumably
has been in Gnus upstream several days before that.

There has been _no_ indication that my report has been read or received
by anybody at all.

The above message by yours is the first such indication (the original
message remains without followup or reply).  It was rather hard to check
for replies/reactions anyway, since the gnus-bug list does not appear on
gmane or other typical mailing list replicators.  One can only look at
news.gnus.org itself.  Finding the information where the gnus bug list
ends up is not easy, either: on
<URL:http://www.gnus.org/resources.html>, you find the sentence

    If you want to report Gnus bugs, you should send them to
    bugs@gnus.org. The bug reports (and responses from the Gnus
    Bugfixing Girls & Boys) can be read from Norway.

The last word in that sentence ("Norway") happens to be a hyperlink with
the news: protocol.  In the unlikely case that your system will resolve
such hyperlinks to your favorite newsreader (an educated guess being
"Gnus"), you'll get there.

Letting your system resolve such links requires a helper application
like


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: emacs-url --]
[-- Type: text/x-sh, Size: 72 bytes --]

#!/bin/sh
/usr/local/bin/emacsclient -a "" --eval "(browse-url \"$1\")"

[-- Attachment #3: Type: text/plain, Size: 377 bytes --]


installed in your binary path and your system knowing about it.  I
should guess that the ratio of Gnus users for which this is the case is
less than 5%.

So the only visible reaction I get after about a week is a chastisement
for thinking something in the bug reporting process appears to be
broken.

To be honest, I am not exactly convinced otherwise yet.

-- 
David Kastrup

  reply	other threads:[~2011-03-14 15:17 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 10:11 David Kastrup
2011-03-14 14:47 ` Lars Magne Ingebrigtsen
2011-03-14 15:17   ` David Kastrup [this message]
2011-03-14 16:12     ` Adam Sjøgren
2011-03-14 17:47       ` Sivaram Neelakantan
2011-03-14 16:22     ` Lars Magne Ingebrigtsen
2011-03-14 19:13 ` message-yank-original issue (was: Gnus bugfixing is broken.) Ted Zlatanov
2011-03-14 19:38   ` message-yank-original issue Antoine Levitt
2011-03-14 19:47     ` Ted Zlatanov
2011-03-14 21:02       ` Antoine Levitt
2011-03-14 22:04         ` Ted Zlatanov
2011-03-15  0:36         ` Michael Welsh Duggan
2011-03-15 15:30         ` Lars Magne Ingebrigtsen
2011-03-15 15:29       ` Lars Magne Ingebrigtsen
2011-03-15 15:49         ` Ted Zlatanov
2011-03-15 15:56           ` Lars Magne Ingebrigtsen
2011-03-15  9:34   ` Ted Zlatanov
2011-03-15  9:48     ` David Kastrup
2011-03-15 10:01       ` Ted Zlatanov
2011-03-26 19:34     ` Sven Joachim
2011-03-28 19:05       ` Ted Zlatanov
2011-03-28 19:57         ` Sven Joachim
2011-03-28 20:06           ` Ted Zlatanov
2011-03-28 20:35         ` Stefan Monnier
2011-03-29  5:37           ` Antoine Levitt
2011-03-28 20:41         ` Stefan Monnier
2011-03-29 14:55           ` Ted Zlatanov
2011-03-29 15:08             ` David Kastrup
2011-03-29 15:20               ` Gnus compatibility with the lexical binding branch (was: message-yank-original issue) Ted Zlatanov
2011-03-29 20:16                 ` Gnus compatibility with the lexical binding branch Stefan Monnier
2011-03-29 20:53                   ` Ted Zlatanov
2011-03-30  0:42                     ` Stefan Monnier
2011-04-08  5:51                       ` Ted Zlatanov
2011-03-15 10:06 ` Gnus bugfixing is broken Ted Zlatanov
2011-03-15 13:31   ` Didier Verna
2011-03-15 13:52     ` Ted Zlatanov
2011-03-15 15:23       ` Lars Magne Ingebrigtsen
2011-03-15 15:56         ` Ted Zlatanov
2011-03-15 16:09           ` Lars Magne Ingebrigtsen
2011-03-15 17:01             ` Didier Verna
2011-03-15 13:58     ` Michael Albinus
2011-03-15 14:46       ` Didier Verna
2011-03-15 14:57         ` Ted Zlatanov
2011-03-15 15:08         ` Michael Albinus

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=87hbb5ivdo.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=ding@gnus.org \
    --cc=larsi@gnus.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.
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 NNTP newsgroup(s).