On Thu, Jan 11, 2018 at 03:15:41PM -0800, Richard Shaffer wrote: > On Thu, Jan 11, 2018 at 2:49 PM, Moritz Barsnick <barsn...@gmx.net> wrote: > > > On Thu, Jan 11, 2018 at 14:28:52 -0800, rshaf...@tunein.com wrote: > > > > > [PATCH 3/3] http: fix memory leak in parse_cookie.g > > > > > This is my first time contributing. > > > > Where are the other two of the three ("3/3") patches then? (Not > > important, but it's confusing on the mailing list.) > > > > I apologize for the 3/3 in the subject. Patches 1 and 2 deal with something > else, and I'll submit those for review later. > > > > > The problem and the solution seem pretty straightforward, but if I'm > > missing something, please do point me in the right direction. > > > > I believe the way you submitted this, this text would be part of your > > commit message. If you desire to type it into the email, please put it > > below the three dashes: > > > Good to know. If someone is willing to review the substance of the patch, > hopefully they'll remove my introduction before committing.
will apply with the commit messages fixed thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB When you are offended at any man's fault, turn to yourself and study your own failings. Then you will forget your anger. -- Epictetus
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel