From: Milan Zamazal <pdm@zamazal.org>
To: GNU GNATS discussions <help-gnats@gnu.org>
Subject: Re: GNATS development services moved to gnu.org
Date: Fri, 12 Oct 2001 11:07:00 -0000 [thread overview]
Message-ID: <87pu6bm86f.fsf@blackbird.zamazal.org> (raw)
In-Reply-To: <20011119100405.B31509@wookimus.net>
>>>>> "CCW" == Chad C Walstrom <chewie@wookimus.net> writes:
CCW> We really didn't have a whole lot of traffic on gnats-devel to
CCW> begin with. If traffic picks up, most likely after the release
CCW> of v4, you can always elect to start up yet another list for
CCW> devel-only discussions.
Exactly.
CCW> Personal preference would have directed me to make (keep)
CCW> gnats-{devel,user,announce,cvs} lists instead of
CCW> {help,info,commit}-gnats, but GNU seems to have a precedence
CCW> with this naming convention.
Yes, the list names must satisfy GNU conventions. And the consistency
of the overall GNU mailing list names has a precedence over old list
names of a particular subproject.
CCW> For example, it'd be a lot easier to find the gnats related
CCW> lists at http://www.gnu.org/pipermail/ were they prefixed with
CCW> the software name instead of the list topic.
OTOH you can find all GNU announcement lists in a single place. And
according to the GNU conventions, the lists info-PROJECT and
help-PROJECT should always exist if there are any mailing lists for
PROJECT there at all.
Regards,
Milan Zamazal
--
real programmer? don't get me started. if you need to hide your
pathetic excuse for a carreer behind super-macho languages like C, C++,
and/or Perl instead of writing clean, maintainable, efficient code, you
aren't much of a real programmer in my view. -- Erik Naggum in comp.emacs
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2001-11-22 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87itc8vtp9.fsf@blackbird.zamazal.org>
2001-10-05 6:33 ` Michael Richardson
2001-10-08 2:31 ` Chad C. Walstrom
2001-10-12 11:07 ` Milan Zamazal [this message]
2001-10-12 15:58 ` Milan Zamazal
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=87pu6bm86f.fsf@blackbird.zamazal.org \
--to=pdm@zamazal.org \
--cc=help-gnats@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).