{"thread":{"id":"27487","subject":"git send-email --body ?","startedAt":"2011-05-27T19:56:24Z","lastAt":"2011-05-28T18:22:16Z","messageCount":2,"participants":["Jim Cromie"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"168895","messageId":"BANLkTi=28buKWVZeAHZs3xB4ry+njDDuuA@mail.gmail.com","threadId":"27487","inReplyTo":null,"subject":"git send-email --body ?","fromName":"Jim Cromie","fromEmail":"jim.cromie@gmail.com","sentAt":"2011-05-27T19:56:24Z","receivedAt":"2011-05-27T19:56:24Z","isPatch":false,"sender":{"key":"jim.cromie@gmail.com","avatar":null},"body":"The perlbug tool is increasingly used by perl community to send patches,\nit has options to save report (perlbug.rep by default)\n\nIve started hacking it to use git send-email when used from inside the git repo\n(theyve switched to git :-), and Id like to just use the file it writes.\n\nI tried just passing file in as 1st arg, tool was unhappy:\n\n[jimc@groucho perl]$ git send-email --dry-run perlbug.rep 0001-*\nfatal: perlbug.rep: 61: patch contains a line longer than 998 characters\nwarning: no patches were sent\n\nI dont want to turn off validation, but if I do, it appears to work,\nbut my test-send resulted in only the 2 patch files 0001-* arriving\nat my inbox, it seems the 1st file (perlbug.rep) was silently rejected.\n\nIndeed, on-screen output shows only 2 sends (below)\n\n--body seems an ideal solution:\nit would read file, and act like --compose if the file were missing\ncritical stuff, or perhaps just error out.\n\nthanks,\n~jimc\n\n[jimc@groucho perl]$ git send-email --to=kidongrok@yahoo.com\n--no-validate perlbug.rep 0001-*\nperlbug.rep\n0001-perlhack.pod-fix-perlbug-invocation.patch\n0001-regexp.h-repair-linux-perf-compilation.patch\n\n Who\nshould the emails appear to be from? [Jim Cromie\n]\nEmails will be sent from: Jim Cromie \n\n\nMessage-ID to be used as In-Reply-To for the first email?\nPassword:\nOK. Log says:\nServer: smtp.gmail.com\nMAIL FROM:\nRCPT TO:\nFrom: Jim Cromie \nTo: kidongrok@yahoo.com\nSubject: [PATCH] b3045a4 perlhack.pod: fix perlbug invocation\nDate: Fri, 27 May 2011 13:22:49 -0600\nMessage-Id: <5.12.3_2182_1306516233@groucho.jimc.earth>\nX-Mailer: git-send-email 1.7.4.4\nReply-To: jim.cromie@gmail.com\n\nResult: 250 2.0.0 OK 1306524179 a6sm721905pbo.15\n\nIn git 1.7.0, the default has changed to --no-chain-reply-to\nSet sendemail.chainreplyto configuration variable to true if\nyou want to keep --chain-reply-to as your default.\n(mbox) Adding cc: Jim Cromie from line 'From:\nJim Cromie '\n\nFrom: Jim Cromie \nTo: kidongrok@yahoo.com\nCc: Jim Cromie \nSubject: [PATCH] perlhack.pod: fix perlbug invocation\nDate: Fri, 27 May 2011 13:22:50 -0600\nMessage-Id: <1306524177-10446-1-git-send-email-jim.cromie@gmail.com>\nX-Mailer: git-send-email 1.7.4.4\nIn-Reply-To: <5.12.3_2182_1306516233@groucho.jimc.earth>\nReferences: <5.12.3_2182_1306516233@groucho.jimc.earth>\n\n The Cc list above has been expanded by additional\n addresses found in the patch commit message. By default\n send-email prompts before sending whenever this occurs.\n This behavior is controlled by the sendemail.confirm\n configuration setting.\n\n For additional information, run 'git send-email --help'.\n To retain the current behavior, but squelch this message,\n run 'git config --global sendemail.confirm auto'.\n\n\n Send this\nemail? ([y]es|[n]o|[q]uit|[a]ll): a\nOK. Log says:\nServer: smtp.gmail.com\nMAIL FROM:\nRCPT TO:\nRCPT TO:\nFrom: Jim Cromie \nTo: kidongrok@yahoo.com\nCc: Jim Cromie \nSubject: [PATCH] perlhack.pod: fix perlbug invocation\nDate: Fri, 27 May 2011 13:22:50 -0600\nMessage-Id: <1306524177-10446-1-git-send-email-jim.cromie@gmail.com>\nX-Mailer: git-send-email 1.7.4.4\nIn-Reply-To: <5.12.3_2182_1306516233@groucho.jimc.earth>\nReferences: <5.12.3_2182_1306516233@groucho.jimc.earth>\n\nResult: 250 2.0.0 OK 1306524208 a6sm721905pbo.15\n\n(mbox) Adding cc: Jim Cromie from line 'From:\nJim Cromie '\nOK. Log says:\nServer: smtp.gmail.com\nMAIL FROM:\nRCPT TO:\nRCPT TO:\nFrom: Jim Cromie \nTo: kidongrok@yahoo.com\nCc: Jim Cromie \nSubject: [PATCH] regexp.h: repair linux perf compilation\nDate: Fri, 27 May 2011 13:22:51 -0600\nMessage-Id: <1306524177-10446-2-git-send-email-jim.cromie@gmail.com>\nX-Mailer: git-send-email 1.7.4.4\nIn-Reply-To: <5.12.3_2182_1306516233@groucho.jimc.earth>\nReferences: <5.12.3_2182_1306516233@groucho.jimc.earth>\n\nResult: 250 2.0.0 OK 1306524210 a6sm721905pbo.15\n"},{"id":"168920","messageId":"BANLkTinPHjON73a37CQD-oT3XWxW4V6=jw@mail.gmail.com","threadId":"27487","inReplyTo":"BANLkTi=28buKWVZeAHZs3xB4ry+njDDuuA@mail.gmail.com","subject":"Re: git send-email --body ?","fromName":"Jim Cromie","fromEmail":"jim.cromie@gmail.com","sentAt":"2011-05-28T18:22:16Z","receivedAt":"2011-05-28T18:22:16Z","isPatch":false,"sender":{"key":"jim.cromie@gmail.com","avatar":null},"body":"On Fri, May 27, 2011 at 1:56 PM, Jim Cromie wrote:\n> The perlbug tool is increasingly used by perl community to send patches,\n> it has options to save report (perlbug.rep by default)\n>\n> Ive started hacking it to use git send-email when used from inside the git repo\n> (theyve switched to git :-), and Id like to just use the file it writes.\n>\n> I tried just passing file in as 1st arg, tool was unhappy:\n>\n> [jimc@groucho perl]$ git send-email --dry-run  perlbug.rep 0001-*\n> fatal: perlbug.rep: 61: patch contains a line longer than 998 characters\n> warning: no patches were sent\n>\n\nNevermind.\n\nperlbug was doing some odd stuff - it wasnt writing headers to saved file,\nso when I went to send it, git-send-email complained.\n\nIve now hacked perlbug to call git-send-email $rptfile @patchfiles,\nwithout --compose, and things work.\n\nsorry for the noise.\n"}]}