Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: ognus
Date: 03 Nov 2000 15:11:06 +0100	[thread overview]
Message-ID: <rju29pxi11.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <vafofzyhtax.fsf@lucy.cs.uni-dortmund.de>

[-- Attachment #1: Type: text/plain, Size: 104 bytes --]


Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> There are CVS commit guidelines? 


[-- Attachment #2.1: Type: text/plain, Size: 101 bytes --]

Subject: Topics

Topics:
   CVS write access policy & nntp gateway & bug reports & stuff
   Re: CVS


[-- Attachment #2.2: Type: text/plain, Size: 1649 bytes --]

Date: 27 Sep 1999 18:40:44 +0200
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: CVS write access policy & nntp gateway & bug reports & stuff
Message-ID: <m34sgg8fzn.fsf_-_@quimbies.gnus.org>
References: <37EF95D0.26891872@orgtek.com> <rxn1u8uy9y.fsf@tick.thecity.home> <m3d7v48ghw.fsf@quimbies.gnus.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

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



[-- Attachment #2.3: Type: text/plain, Size: 1338 bytes --]

Date: 07 Nov 1999 07:27:11 +0100
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: CVS
Message-ID: <m3hfiyvmtc.fsf@quimbies.gnus.org>
References: <rjemeo7tz3.fsf@feller.dina.kvl.dk> <874sfklpbc.fsf@pc-hrvoje.srce.hr> <m3ln8bcl7b.fsf@quimbies.gnus.org> <vaf7ljvuo36.fsf@lucy.cs.uni-dortmund.de> <m3so2jugdo.fsf@quimbies.gnus.org> <rjvh7f2aom.fsf_-_@feller.dina.kvl.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> I'd feel safer if there were some rules for cvs writes.  
> 
> For auctex, I use:
> 
> 1. People can update the files they "own", but should post to the list
>    when they do.
> 
> 2. Updates to shared files requeres an ok from me.  Not for the
>    specific code, just for the idea.

Ok, these are the rules:

1. You have full responsibility for the files you "own"

2. Fix any bugs you want.  (Especially you, Shenghuo.  :-)

3. New features or major stuff should either have an OK from me before
   they are checked in, or they should be discussed here, and people here
   should think it's a good idea.  (If I really hate it, I'll back it out
   again, anyway)

4. If you're unsure, ask me or ask here before checking in

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen



  reply	other threads:[~2000-11-03 14:11 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-27 22:59 ognus Simon Josefsson
2000-10-28  0:25 ` ognus ShengHuo ZHU
2000-10-28 13:41   ` ognus Simon Josefsson
2000-10-28 15:34     ` ognus Kai Großjohann
2000-10-28 15:41       ` ognus Simon Josefsson
2000-10-29 17:47       ` ognus Dave Love
2000-10-31 22:09     ` S/MIME and PGP/MIME (Was: Re: ognus) Bjørn Mork
2000-10-31 23:18       ` ShengHuo ZHU
2000-11-01 20:41         ` Bjørn Mork
2000-10-28 19:22   ` emacs21-branch (Re: ognus) Karl Eichwalder
2000-10-29 17:47     ` Dave Love
2000-10-29 18:48     ` Karl Eichwalder
2000-10-29 19:50       ` Kai Großjohann
2000-10-29 21:26         ` Florian Weimer
2000-10-29 22:53         ` ShengHuo ZHU
2000-10-30 22:53         ` Dave Love
2000-10-30 23:20           ` Denys Duchier
2000-10-30 23:38             ` Laura Conrad
2000-10-31  9:50               ` Denys Duchier
2000-11-02 17:25                 ` Dave Love
2000-11-02 17:34                   ` Gunnar Evermann
2000-11-03 19:09                     ` Dave Love
2000-11-03 22:07                       ` Gunnar Evermann
2000-11-02 21:01                   ` Denys Duchier
2000-11-02 22:53                     ` Kai Großjohann
2000-11-03 14:31                       ` Per Abrahamsen
2000-11-03 14:42                         ` luis fernandes
2000-11-04 11:42                         ` Steinar Bang
2000-11-04  2:52                       ` Russ Allbery
2000-11-03 19:14                     ` Dave Love
2000-11-03 19:42                       ` Denys Duchier
2000-11-04  0:04                         ` Kai Großjohann
2000-11-04 15:04                         ` Per Abrahamsen
2000-11-04 20:15                           ` Denys Duchier
2000-11-04 22:59                             ` Andreas Fuchs
2000-11-05  1:15                           ` Russ Allbery
2000-11-02 17:23             ` Dave Love
2000-10-31  0:17           ` Steven E. Harris
2000-10-31 10:09           ` Kai Großjohann
2000-10-29 17:39   ` ognus Dave Love
2000-10-30 11:35     ` ognus Per Abrahamsen
2000-10-30 13:05       ` ognus Kai Großjohann
2000-10-30 23:24         ` ognus Dave Love
2000-10-31 10:16           ` ognus Kai Großjohann
2000-11-04 20:23             ` ognus Lars Magne Ingebrigtsen
2000-11-04 22:04               ` ognus Kai Großjohann
2000-11-04 22:34                 ` ognus Lars Magne Ingebrigtsen
2000-10-30 23:22       ` ognus Dave Love
2000-10-31  9:07         ` ognus Russ Allbery
2000-10-31 13:06           ` ognus Karl Kleinpaste
2000-10-31 17:00           ` ognus Sean Doran
2000-10-31 17:55             ` ognus Kai Großjohann
2000-10-31 13:36         ` ognus Per Abrahamsen
2000-10-31 16:49           ` ognus Sean Doran
2000-11-02 17:35           ` ognus Dave Love
2000-11-02 18:08             ` ognus ShengHuo ZHU
2000-11-02 19:31               ` uunassigned code (was: Re: ognus) Per Abrahamsen
2000-11-03 19:01               ` ognus Dave Love
2000-11-02 19:18             ` ognus Per Abrahamsen
2000-11-02 23:01               ` ognus Kai Großjohann
2000-11-03 14:11                 ` Per Abrahamsen [this message]
2000-11-03 19:04               ` ognus Dave Love
2000-11-04 15:11                 ` ognus Per Abrahamsen
2000-11-03 15:39             ` ognus Simon Josefsson
2000-11-04 20:31             ` ognus Lars Magne Ingebrigtsen
2000-10-31 16:37         ` ognus Sean Doran
2000-11-02 17:22           ` ognus Dave Love
2000-11-04 11:48         ` ognus Steinar Bang
2000-11-04 11:45       ` ognus Steinar Bang

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=rju29pxi11.fsf@ssv2.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).