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/[email protected]/
[ncc-services-wg] Pre-PDP discussion: "All published documents and PDPs are maintained with git"
- Previous message (by thread): [ncc-services-wg] let's use git for everything: it can always be changed later
- 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:23:33 CET 2013
On Fri, Mar 15, 2013 at 8:13 PM, Richard Hartmann <richih.mailinglist at gmail.com> wrote: > All PDPs will be maintained as a separate branch. Every new version > of a PDP is an update within that branch. The branch will either be > merged back into master or left unmerged but intact, depending on if > they are accepted or not. To make this point clear: I am not saying that a proposer should be forced to know git. If RIPE NCC receives the proposal/update as simple text file, it should import that data into git (retaining author information) and commit the result. Or nudge the proposer into the right direction if need be. Again, I will help with the git side of things for at least 12 months if this proposal is accepted. Richard
- Previous message (by thread): [ncc-services-wg] let's use git for everything: it can always be changed later
- 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 ]