On Fri, Nov 08, 2019 at 03:25:00PM +0100, Dmitry Vyukov wrote:
>
> It has the format=flowed; delsp=yes part:
>
> Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes
>
> Which according to https://tools.ietf.org/html/rfc3676 seems to mean
> that that line is not wrapped: new line
On Fri, Nov 08, 2019 at 10:44:37PM +1100, Daniel Axtens wrote:
> Don Zickus writes:
>
> > On Thu, Nov 07, 2019 at 02:35:08AM +1100, Daniel Axtens wrote:
> >> > As soon as we have a bridge from plain-text emails into the structured
> >> > form, we can start building everything else in the
> I'm actually very interested in seeing patchwork switch from being fed
> mail directly from postfix to using public-inbox repositories as its
> source of patches. I know it's easy enough to accomplish as-is, by
> piping things from public-inbox to parsemail.sh, but it would be even
> more
Hi Ted,
On Fri, Nov 08, 2019 at 09:02:49AM -0500, Theodore Y. Ts'o wrote:
> On Fri, Nov 08, 2019 at 10:44:25AM +0100, Dmitry Vyukov wrote:
> > syzbot asks to provide fixing commit in a particular format (and on 1
> > line, otherwise not possible to parse back).
> >
> > It sent this yesterday:
>
On Fri, Nov 08, 2019 at 03:12:51PM +0100, Dmitry Vyukov wrote:
> Just to clarify: syzbot does not do this on purpose. It generates and
> hands off unwrapped lines. The "format=flowed; delsp=yes" part was
> done by somebody else.
Looks like vger received it already mangled:
Hi Daniel,
On 31.10.19 14:42, Daniel Axtens wrote:
> Mete Polat writes:
>
>> Move the series patch list from 'Related' to 'Series' and display the
>> series name, its patches and a detailed link in the same row. This
>> allows to use the 'Related' row for actually showing submission
>>
Don Zickus writes:
> On Thu, Nov 07, 2019 at 02:35:08AM +1100, Daniel Axtens wrote:
>> > As soon as we have a bridge from plain-text emails into the structured
>> > form, we can start building everything else in the structured world.
>> > Such bridge needs to parse new incoming emails, try to
