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 22:58:39 CET 2013
On Fri, Mar 15, 2013 at 10:54 PM, Sander Steffann <sander at steffann.nl> wrote: > Please stop thinking in solutions, and start thinking in requirements. I was answering your specific questions, but I see your point. > - No CLI, knowing of filenames or such things must be necessary CLI offers this, you are not forced to use CLI to arrive at this. If you know you want to compare ripe-XXX and ripe-YYY, you have the file names. How could you compare two files without knowing their file names? > - A way must be provided for users to clone the RIPE document repository and perform the same analysis as the RIPE NCC offers on their own system That is one of the pivotal points of my proposal. Please note the anonymous pull I explicitly mention in the proposal. When I say "CLI", I mean "CLI on your own computer on a fully offline clone of all data". -- 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 ]