Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Bug reporting
Date: Wed, 31 Aug 2011 15:09:27 -0500	[thread overview]
Message-ID: <87k49tmjgo.fsf@lifelogs.com> (raw)
In-Reply-To: <87liu9nyf2.fsf@gnus.org>

On Wed, 31 Aug 2011 22:01:05 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote: 

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

LI> I'm like doing my day job at the moment.  Bug-fixing service will resume
LI> in a few days.

Ditto; sorry for the lack of response from me for a while now.  I'm
digging myself out of a pile of kittehs^H^H^H^H^H^H^Hwork after moving
recently.

Ted




  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 [this message]
2011-09-01  7:27     ` Dave Abrahams
2011-08-31 20:09 ` Andrew Cohen
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=87k49tmjgo.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).