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:10:09 CET 2013
On Fri, Mar 15, 2013 at 9:07 PM, Rob Evans <rhe at nosc.ja.net> wrote: > Whilst understanding the limits and overheads of rsync, I'd have thought there is enough experience of the software within the NCC (think RPKI) to be able to set up an rsync server for the documents fairly trivially. There are several different technologies which provide some or all of the features git offers. Yet, the package as a whole is unmatched, imo. I am well aware that this is the weakest of all proposals as it specifies a specific piece of software that should be used. I still think it would be a Very Good Thing, but if this one fails and the others come through, I will be happy. -- 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 ]