{"comment":{"user":{"login":"mporsch","id":1180665,"url":"https://api.github.com/users/mporsch","avatar_url":"https://secure.gravatar.com/avatar/1b44d7aa5d63821aa32922ca3bda4899?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"1b44d7aa5d63821aa32922ca3bda4899"},"created_at":"2011-12-24T11:00:42Z","path":null,"updated_at":"2011-12-24T11:00:42Z","id":819290,"html_url":"https://github.com/zps/greenmesh/commit/37e1814821#commitcomment-819290","position":null,"body":"Did you re-type everything by hand? There is a git function for fetching patches/RFCs which have been sent with git send-email. But I also haven't used that yet.\r\n\r\nYou mix the use of \"method\" and \"protocol\". The standard always says \"method\".\r\n\r\nAlso the standard never mentions \"Time Synchronization\".\r\n\r\nCopy-paste error\r\n+ * @time_sync_method: which time synchronization metric to use\r\n\r\n\r\nI see no other differences to the mailing lists RFC. So you could as well use that. I can also re-send it as attachment if you prefer.","url":"https://api.github.com/repos/zps/greenmesh/comments/819290","line":null,"commit_id":"37e1814821fce8a9fad49c62eb4f1da406aeee48"}}