{"action":"created","issue":{"url":"https://api.github.com/repos/golang/go/issues/9522","labels_url":"https://api.github.com/repos/golang/go/issues/9522/labels{/name}","comments_url":"https://api.github.com/repos/golang/go/issues/9522/comments","events_url":"https://api.github.com/repos/golang/go/issues/9522/events","html_url":"https://github.com/golang/go/issues/9522","id":53560594,"number":9522,"title":"git-codereview: git change should barf if there is no newline between subject and description","user":{"login":"davecheney","id":7171,"avatar_url":"https://avatars.githubusercontent.com/u/7171?v=3","gravatar_id":"","url":"https://api.github.com/users/davecheney","html_url":"https://github.com/davecheney","followers_url":"https://api.github.com/users/davecheney/followers","following_url":"https://api.github.com/users/davecheney/following{/other_user}","gists_url":"https://api.github.com/users/davecheney/gists{/gist_id}","starred_url":"https://api.github.com/users/davecheney/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davecheney/subscriptions","organizations_url":"https://api.github.com/users/davecheney/orgs","repos_url":"https://api.github.com/users/davecheney/repos","events_url":"https://api.github.com/users/davecheney/events{/privacy}","received_events_url":"https://api.github.com/users/davecheney/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-01-06T20:42:23Z","updated_at":"2015-01-06T22:10:31Z","closed_at":null,"body":"Gerrit makes a complete hash of the CL if there is no blank line between the 1st and subsequent lines on the change description. Maybe git-codereview should detect this and barf accordingly."},"comment":{"url":"https://api.github.com/repos/golang/go/issues/comments/68943446","html_url":"https://github.com/golang/go/issues/9522#issuecomment-68943446","issue_url":"https://api.github.com/repos/golang/go/issues/9522","id":68943446,"user":{"login":"davecheney","id":7171,"avatar_url":"https://avatars.githubusercontent.com/u/7171?v=3","gravatar_id":"","url":"https://api.github.com/users/davecheney","html_url":"https://github.com/davecheney","followers_url":"https://api.github.com/users/davecheney/followers","following_url":"https://api.github.com/users/davecheney/following{/other_user}","gists_url":"https://api.github.com/users/davecheney/gists{/gist_id}","starred_url":"https://api.github.com/users/davecheney/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davecheney/subscriptions","organizations_url":"https://api.github.com/users/davecheney/orgs","repos_url":"https://api.github.com/users/davecheney/repos","events_url":"https://api.github.com/users/davecheney/events{/privacy}","received_events_url":"https://api.github.com/users/davecheney/received_events","type":"User","site_admin":false},"created_at":"2015-01-06T22:10:31Z","updated_at":"2015-01-06T22:10:31Z","body":"I think that warning comes from the gerrit end which doesn't like any lines\r\n> 70 chars.\r\n\r\nI think the git-codereview tool could do more before involving gerrit.\r\nOn 7 Jan 2015 09:07, \"Richard L. Hudson\" <notifications@github.com> wrote:\r\n\r\n> When I did this I got a warning about the subject being too long. The next\r\n> change has a fixed subject line.\r\n>\r\n> git mail -r rsc@golang.org,austin@google.com\r\n> remote: Resolving deltas: 100% (8/8)\r\n> remote: Processing changes: new: 1, done\r\n> remote: (W) aa88053: commit subject >65 characters; use shorter first\r\n> paragraph\r\n> remote: (W) aa88053: too many commit message lines longer than 70\r\n> characters; manually wrap lines\r\n> remote:\r\n> remote: New Changes:\r\n> remote: https://go-review.googlesource.com/2349 Runtime: Increase GC\r\n> concurrency. Run GC in its own\r\n> background goroutine ...\r\n> remote:\r\n>\r\n>\r\n> On Tue, Jan 6, 2015 at 3:42 PM, Dave Cheney <notifications@github.com>\r\n> wrote:\r\n>\r\n> > Gerrit makes a complete hash of the CL if there is no blank line between\r\n> > the 1st and subsequent lines on the change description. Maybe\r\n> > git-codereview should detect this and barf accordingly.\r\n> >\r\n> > —\r\n> > Reply to this email directly or view it on GitHub\r\n> > <https://github.com/golang/go/issues/9522>.\r\n> >\r\n>\r\n> —\r\n> Reply to this email directly or view it on GitHub\r\n> <https://github.com/golang/go/issues/9522#issuecomment-68943046>.\r\n>"}}