On Fri, May 27, 2011 at 1:56 PM, Jim Cromie <jim.cromie@xxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html