Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Subject: Re: Parsing of Kai's Emails fails now completlty
Date: Sun, 11 May 2003 15:05:16 +0100	[thread overview]
Message-ID: <rzqd6ipshnn.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: <m34r45xbqw.fsf@hamster.pflaesterer.de> ( =?iso-8859-1?q?Karl_Pfl=E4sterer's_message_of?= "Fri, 09 May 2003 01:34:47 +0200")

sigurd@12move.de (Karl Pflästerer) writes:

> I'll try the CVS head version tommorrow.  Regarding the bug address: I
> used all the time the ding list to report bugs (as a lot of other people
> too).

Maybe I'm confused about its purpose.  If that's what people should
do, I think the bugs address should be redirected here.

> It was never said before that this should be wrong.  But I now
> subscribed also the gnus bugs ng on gmane.

You certainly shouldn't need to subscribe to a bugs list if you report
bugs.  It's a bug if people responding don't copy responses to the
submitter.  (I know they often don't.)

> Well that's the risk of using beta versions. I didn't want to complain
> because it's only my risk if I use a beta version 

Please complain (for useful values of `complain')!  You're right that
there's a risk to using test versions -- and I think people are too
often encouraged to do that -- but if you're willing to, the feedback
should be very welcome.  Thanks.



  reply	other threads:[~2003-05-11 14:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04 12:24 Andreas Jaeger
2003-05-04 15:42 ` Xavier Maillard
2003-05-04 19:13   ` Andreas Jaeger
2003-05-06 20:25     ` Xavier Maillard
2003-05-06 22:46       ` Reiner Steib
2003-05-06 23:24       ` Karl Pflästerer
2003-05-08 22:48         ` Dave Love
2003-05-08 23:34           ` Karl Pflästerer
2003-05-11 14:05             ` Dave Love [this message]
2003-05-09  7:15           ` Andreas Jaeger
2003-05-09 16:21             ` Karl Pflästerer
2003-05-07  5:34       ` Andreas Jaeger
2003-05-04 19:50 ` Christoph Garbers

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=rzqd6ipshnn.fsf@albion.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    /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).