From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: CVS write access policy & nntp gateway & bug reports & stuff
Date: 27 Sep 1999 18:40:44 +0200 [thread overview]
Message-ID: <m34sgg8fzn.fsf_-_@quimbies.gnus.org> (raw)
In-Reply-To: <m3d7v48ghw.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> (And we're still testing the news-to-mail thing.)
Hey! It worked!
Anybody can now access the quimby.gnus.org news server. Gatewaying
back and forth seems to work ok, so anyone who want to use it -- feel
free.
CVS read policy: Anyone who wants to check things out of the CVS
thing -- go ahead.
CVS write policy: People who have write access can check things into
the repository whenever they feel like it. Before doing a release, I
will be going over the diff and chucking out anything I don't like,
but if nobody puts in things I don't like, that will make things
easier for me. :-) But you have my confidence. Oh, but pleeeze --
please update the ChangeLog when you do any changes.
Perhaps a pgnus-current.tar.gz package should be created once a day --
just a CVS checkout, and then tarred and gzipped?
All bug reports go to the gnus-bug newsgroup. Perhaps this group
shouldn't be open for reading for the entire world, since there might
be sensitive information there? How about password-protecting that
group, but with a "public" password that people on this list knows
about?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-09-27 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-27 16:05 just tried making 0.97 Daniel Monjar
1999-09-27 16:14 ` Ted Rathkopf
1999-09-27 16:29 ` Lars Magne Ingebrigtsen
1999-09-27 16:40 ` Lars Magne Ingebrigtsen [this message]
1999-10-04 15:59 ` CVS write access policy & nntp gateway & bug reports & stuff Wes Hardaker
1999-10-08 15:43 ` Robert Bihlmeyer
1999-09-27 17:00 ` just tried making 0.97 Stainless Steel Rat
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=m34sgg8fzn.fsf_-_@quimbies.gnus.org \
--to=larsi@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).