Gnus development mailing list
 help / color / mirror / Atom feed
From: Andrew Cohen <cohen@andy.bu.edu>
To: ding@gnus.org
Subject: Re: Bug reporting
Date: Wed, 31 Aug 2011 16:09:25 -0400	[thread overview]
Message-ID: <87bov5wdfu.fsf@andy.bu.edu> (raw)
In-Reply-To: <m2r541icxq.fsf@boostpro.com>

>>>>> "Dave" == Dave Abrahams <dave@boostpro.com> writes:

    Dave> I've been reporting bugs (lots of them, recently) via `M-x
    Dave> gnus-bug' but most of those reports have gotten no attention.
    Dave> Should I be reporting those things here instead, or should I
    Dave> just be more patient, or...?

I look at them on rare occasions (and have even fixed a couple). I'm
responding here mostly because I want to ask if there is some way for me
to mark them fixed? Send an email to Lars? 

(If thats the case, 9271 and 9272 are now fixed, and a fix for 9386 will be
pushed shortly).




  parent reply	other threads:[~2011-08-31 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 19:44 Dave Abrahams
2011-08-31 20:01 ` Lars Ingebrigtsen
2011-08-31 20:09   ` Ted Zlatanov
2011-09-01  7:27     ` Dave Abrahams
2011-08-31 20:09 ` Andrew Cohen [this message]
2011-08-31 20:16   ` David Engster
2011-08-31 20:26     ` Andrew Cohen

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=87bov5wdfu.fsf@andy.bu.edu \
    --to=cohen@andy.bu.edu \
    --cc=ding@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).