The danger of piping an mbox to patch is that it contains more than
authorJarkko Hietaniemi <jhi@iki.fi>
Sun, 16 Apr 2006 11:19:25 +0000 (14:19 +0300)
committerNicholas Clark <nick@ccl4.org>
Mon, 17 Apr 2006 10:24:58 +0000 (10:24 +0000)
commit2d78db9da3a2e0242b1652394b939dc5b5fab5e5
tree88e0c83d60a5a85490235df80f82c31fe4092178
parent77cb431f8c908a31b286bd0ba26649cb6041bd72
The danger of piping an mbox to patch is that it contains more than
one message. So both:

Subject: [PATCH] doop.c: one more code path where memory could leak (Coverity)
Message-Id: <20060416081925.680336CF2D@aprikoosi.hut.fi>
Date: Sun, 16 Apr 2006 11:19:25 +0300 (EEST)

and

Subject: [PATCH] doop.c: one more code path where memory could leak (Coverity)
From: jhi@cc.hut.fi (Jarkko Hietaniemi)
Message-Id: <20060416081925.680336CF2D@aprikoosi.hut.fi>
Date: Sun, 16 Apr 2006 11:19:25 +0300 (EEST)

p4raw-id: //depot/perl@27856
doop.c