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] git is the answer: now what was the question?
- Previous message (by thread): [ncc-services-wg] git is the answer: now what was the question?
- 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 23:17:48 CET 2013
On Fri, Mar 15, 2013 at 11:13 PM, Jim Reid <jim at rfc1035.com> wrote: > Your emails on this topic are NOT doing that at all. They're doing the very opposite. You've already decided that git is the solution to everything. As yet it's not clear what problem needs fixing. [Or if there's a consensus that this problem does indeed need fixing.] I suggest you focus on that. I stated initially that I was aware that this is the weakest of my proposals. I also agreed to switch over to defining requirements. Do I still expect git to be the solution? Yes. Do I want to dive into a meta-discussion about points I already conceded during a fast-paced discussion? No. Richard
- Previous message (by thread): [ncc-services-wg] git is the answer: now what was the question?
- 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 ]