Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Is this the correct place to post patches?
Date: Thu, 11 Dec 2003 10:22:21 +0100	[thread overview]
Message-ID: <v9ad5zvhde.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87fzfs6nvc.fsf@jay.local.invalid>

On Thu, Dec 11 2003, Jeremy Maitin-Shepard wrote:

| Is this the correct place to post patches?

Probably it's better to send them to the Ding (Gnus developers) List
<ding@gnus.org> [1] or use the bug-report interface (`M-x gnus-bug
RET') [2].

BTW, your Message-Id is b0rked.  "jay.local.invalid" isn't a valid
FQDN.  See e.g. `message-user-fqdn' and (info "(message)News
Headers").

Bye, Reiner.

[1] http://news.gmane.org/gmane.emacs.gnus.general
    nntp://news.gmane.org/gmane.emacs.gnus.general

[2] nntp://news.gnus.org/gnus.gnus-bugs
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/


           reply	other threads:[~2003-12-11  9:22 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87fzfs6nvc.fsf@jay.local.invalid>]

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=v9ad5zvhde.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).