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/ncc-services-wg@ripe.net/
[ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Hartmann
richih.mailinglist at gmail.com
Fri Mar 15 21:03:20 CET 2013
On Fri, Mar 15, 2013 at 8:56 PM, Sander Steffann <sander at steffann.nl> wrote: > I don't know how useful this is, as RIPE documents don't change once they are published. If a revision of a RIPE document is published it gets a new number. So I don't think a version control system will be useful here. While that is true, this will still allow anyone to see how PDPs progressed and resulted in new documents. Also, I don't think the power of a single, canonical resource that you can easily sync to your local machines and which you _know_ is up to date should be underestimated. We shouldn't discard using a toold just because we won't need all features it provides. Thanks for your quick feedback, Richard
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]