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] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
- Next message (by thread): [ncc-services-wg] git is the answer: now what was the question?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Fri Mar 15 23:13:07 CET 2013
On 15 Mar 2013, at 21:55, Richard Hartmann <richih.mailinglist at gmail.com> wrote: >> You also appear to be defining outcomes before the requirements are agreed. Or even clear. Let's first understand what problem needs solved and then decide what's the best way to solve them. > > That's what we are doing. To arrive at that, we need something to base > our discussion on. If I hadn't proposed the above, we would not be > having this conversation. 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.
- 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] git is the answer: now what was the question?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]