This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
Maintainer creation policy
- Previous message (by thread): Maintainer creation policy
- Next message (by thread): Maintainer creation policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Poul-Henning Kamp
phk at critter.freebsd.dk
Tue Dec 29 14:52:16 CET 1998
It sounds to me like it would be a better solution to make a person object maintain itself in the absense of any other maintainer, basically changing to rules such that: A person object can have either a maintainer or an authentication mechanism (password/mailfrom or pgp) That would prevent a doubling of the number of records in the database. -- Poul-Henning Kamp FreeBSD coreteam member phk at FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal
- Previous message (by thread): Maintainer creation policy
- Next message (by thread): Maintainer creation policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]