{"action":"created","issue":{"url":"https://api.github.com/repos/git-multimail/git-multimail/issues/108","labels_url":"https://api.github.com/repos/git-multimail/git-multimail/issues/108/labels{/name}","comments_url":"https://api.github.com/repos/git-multimail/git-multimail/issues/108/comments","events_url":"https://api.github.com/repos/git-multimail/git-multimail/issues/108/events","html_url":"https://github.com/git-multimail/git-multimail/issues/108","id":94143051,"number":108,"title":"Rendering of some (unorthodox) commit summaries is sub-ideal","user":{"login":"pfalcon","id":500451,"avatar_url":"https://avatars.githubusercontent.com/u/500451?v=3","gravatar_id":"","url":"https://api.github.com/users/pfalcon","html_url":"https://github.com/pfalcon","followers_url":"https://api.github.com/users/pfalcon/followers","following_url":"https://api.github.com/users/pfalcon/following{/other_user}","gists_url":"https://api.github.com/users/pfalcon/gists{/gist_id}","starred_url":"https://api.github.com/users/pfalcon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pfalcon/subscriptions","organizations_url":"https://api.github.com/users/pfalcon/orgs","repos_url":"https://api.github.com/users/pfalcon/repos","events_url":"https://api.github.com/users/pfalcon/events{/privacy}","received_events_url":"https://api.github.com/users/pfalcon/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-09T20:15:34Z","updated_at":"2015-07-09T20:40:45Z","closed_at":null,"body":"We use git-multimail on mirror of https://github.com/gcc-mirror/gcc . Commit message there don't follow git guidelines, and are heritage of ChangeLog file format. There're commits like https://github.com/gcc-mirror/gcc/commit/75c3f230cd53f464ed35a069842447d577167969 which lead to git-multimail messages like:\r\n\r\n~~~~\r\n      from  75c3f23   \t* genmatch.c (fprintf_indent): New function. \t(operand::gen_transform): Add indent parameter. \t(expr::gen_transform, c_expr::gen_transform, \tcapture::gen_transform): Ditto and use fprintf_indent. \t(dt_node::gen, dt_node::gen_kids, dt_node::gen_kids_1): Ditto. \t(dt_operand::gen, dt_operand::gen_predicate, \tdt_operand::gen_match_op, dt_operand::gen_gimple_expr, \tdt_operand::gen_generic_expr, dt_simplify::gen): Ditto. \t(decision_tree::gen_gimple): Adjust calls and inde [...]\r\n       new  853a01d   2015-07-09  Vladimir Makarov  <vmakarov@redhat.com>\r\n~~~~\r\n\r\nIt would be to have an option to force usage of single first line as summary (vs git convention that summary is separate from details with a blank line, with an extreme case of summary being multi-line).\r\n"},"comment":{"url":"https://api.github.com/repos/git-multimail/git-multimail/issues/comments/120138791","html_url":"https://github.com/git-multimail/git-multimail/issues/108#issuecomment-120138791","issue_url":"https://api.github.com/repos/git-multimail/git-multimail/issues/108","id":120138791,"user":{"login":"moy","id":14709,"avatar_url":"https://avatars.githubusercontent.com/u/14709?v=3","gravatar_id":"","url":"https://api.github.com/users/moy","html_url":"https://github.com/moy","followers_url":"https://api.github.com/users/moy/followers","following_url":"https://api.github.com/users/moy/following{/other_user}","gists_url":"https://api.github.com/users/moy/gists{/gist_id}","starred_url":"https://api.github.com/users/moy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/moy/subscriptions","organizations_url":"https://api.github.com/users/moy/orgs","repos_url":"https://api.github.com/users/moy/repos","events_url":"https://api.github.com/users/moy/events{/privacy}","received_events_url":"https://api.github.com/users/moy/received_events","type":"User","site_admin":false},"created_at":"2015-07-09T20:40:45Z","updated_at":"2015-07-09T20:40:45Z","body":"I guess truncating the summary line to ~70 characters could fix this. I won't have time to work on this soon, but it should be a minor patch to `generate_summaries`, either calling git with a format like `--format='%h %<(100,trunc)%s` and trimming trailing whitespaces after, or doing the elipsis from Python.\r\n\r\nDon't hesitate to ask for help if you try to implement this."}}