{"thread":{"id":"17224","subject":"[RFC] Making format-patch output better when blank line is missing?","startedAt":"2009-01-17T12:35:45Z","lastAt":"2009-01-17T15:47:11Z","messageCount":2,"participants":["Adeodato Simó","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"100823","messageId":"20090117123545.GA22842@chistera.yi.org","threadId":"17224","inReplyTo":null,"subject":"[RFC] Making format-patch output better when blank line is missing?","fromName":"Adeodato Simó","fromEmail":"dato@net.com.org.es","sentAt":"2009-01-17T12:35:45Z","receivedAt":"2009-01-17T12:35:45Z","isPatch":false,"sender":{"key":"dato@net.com.org.es","avatar":"https://gravatar.com/avatar/952ec7d5d5663eb8baf631b5c37f9c58480a881920dd5f8a2d3a71f969b72b53?d=mp&s=160"},"body":"Hello,\n\nI'm using git-format-patch to send commit diff emails, and it was\nrecently brought to my atention that if a commit message consists\nentirely in a paragraph with no blank lines (particluarly, no blank line\nafter the first line, which is not a summary but just the first line of\nthe paragraph), git-format-patch will place all the commit message in\nthe Subject, which is inconvenient to read.\n\nDo you think it would be good to have format-patch do something like\nthis in this case?:\n\n    Subject: [PATCH] This commit introduces a new function bla() that [...]\n\n    [...] makes it possible to apply the frobniz operation to objects\n    that don't bla bla bla bla.\n\n(I realize that, with this, the applying logic would have to learn about\nit. Hm.)\n\n-- \nAdeodato Simó                                     dato at net.com.org.es\nDebian Developer                                  adeodato at debian.org\n \n- I love you, Shirley, I'm not ashamed to say.\n- If you love me, then you'll want me to be happy. Even if I'm not with you.\n- I don't love you that much.\n                -- Denny Crane and Shirley Schmidt\n"},{"id":"100844","messageId":"20090117154711.GD27071@coredump.intra.peff.net","threadId":"17224","inReplyTo":"20090117123545.GA22842@chistera.yi.org","subject":"Re: [RFC] Making format-patch output better when blank line is missing?","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-01-17T15:47:11Z","receivedAt":"2009-01-17T15:47:11Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sat, Jan 17, 2009 at 01:35:45PM +0100, Adeodato Simó wrote:\n\n> I'm using git-format-patch to send commit diff emails, and it was\n> recently brought to my atention that if a commit message consists\n> entirely in a paragraph with no blank lines (particluarly, no blank line\n> after the first line, which is not a summary but just the first line of\n> the paragraph), git-format-patch will place all the commit message in\n> the Subject, which is inconvenient to read.\n\nYeah, such messages don't really interact well with the idea of a\nsubject/body commit format.\n\n> Do you think it would be good to have format-patch do something like\n> this in this case?:\n> \n>     Subject: [PATCH] This commit introduces a new function bla() that [...]\n> \n>     [...] makes it possible to apply the frobniz operation to objects\n>     that don't bla bla bla bla.\n> \n> (I realize that, with this, the applying logic would have to learn about\n> it. Hm.)\n\nI think it would be more readable to simply limit the subject line, add\n\"...\", and then repeat the whole paragraph in the body. Then worst case,\nthe person applying just gets the text repeated, like:\n\n  This commit introduces a new function bla() that...\n\n  This commit introduces a new function bla() that makes it possible to\n  aply the forbniz operation to objects that don't bla bla bla bla.\n\nwhich is actually pretty reasonable. And best case, the person applying\nfixes it up appropriately. But I don't know if it is worth trying to\ncome up with a reversible format. Patches sent through email are meant\nto preserve what's on the other end, but it doesn't _have_ to be exact,\nespecially in the face of somebody ignoring the workflow conventions\nthat the patch format is meant to support.\n\n-Peff\n"}]}