From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Where to send patches against Gnus CVS?
Date: Sat, 17 May 2003 17:51:31 +0200 [thread overview]
Message-ID: <m3d6ih1sho.fsf@defun.localdomain> (raw)
In-Reply-To: <llx5pv6c.fsf@smtpmail.t-online.de>
Adrian Aichner <adrian@xemacs.org> writes:
> What's the email address I should use to send my patcher-mail patch?
>
> ding-patches@gnus.org
I think that's a read-only list for cvs-commits (i.e. not the right
place).
> ding@gnus.org
> seem likely contenders?
Either that or bugs@gnus.org.
(Readers of ding@gnus.org normally assume that you're subscribed to
the list. If you aren't then bugs@gnus.org is probably better).
prev parent reply other threads:[~2003-05-17 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 13:19 Adrian Aichner
2003-05-17 15:51 ` Jesper Harder [this message]
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=m3d6ih1sho.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).