From: Jim Cromie <jim.cromie@gmail.com>
Date: Sat, 28 May 2011 18:22:16 GMT
Subject: Re: git send-email --body <file> ?
Message-ID: <BANLkTinPHjON73a37CQD-oT3XWxW4V6=jw@mail.gmail.com>
In-Reply-To: <BANLkTi=28buKWVZeAHZs3xB4ry+njDDuuA@mail.gmail.com>

On Fri, May 27, 2011 at 1:56 PM, Jim Cromie <jim.cromie@gmail.com> wrote:
> The perlbug tool is increasingly used by perl community to send patches,
> it has options to save report (perlbug.rep by default)
>
> Ive started hacking it to use git send-email when used from inside the git repo
> (theyve switched to git :-), and Id like to just use the file it writes.
>
> I tried just passing file in as 1st arg, tool was unhappy:
>
> [jimc@groucho perl]$ git send-email --dry-run  perlbug.rep 0001-*
> fatal: perlbug.rep: 61: patch contains a line longer than 998 characters
> warning: no patches were sent
>

Nevermind.

perlbug was doing some odd stuff - it wasnt writing headers to saved file,
so when I went to send it, git-send-email complained.

Ive now hacked perlbug to call git-send-email $rptfile @patchfiles,
without --compose, and things work.

sorry for the noise.