* Paul Elliott [130829 22:24]:
> > As a workaround till this is fixedI suggest starting each commit with
> > a single line followed by an empty line. (As suggested by the DISCUSSION
> > section of git-commit(1)).
>
> That does not work. The dep-3 standard clearly states:
> "A header always
On Thu, Aug 29, 2013 at 08:26:12PM +0200, Bernhard R. Link wrote:
> * Paul Elliott [130829 03:35]:
> > Ok I will send you an example. [...]
> > Tell me if this example is helpfull.
>
> Yes, it is helpful. That seems to be a ugly effect of git wanting to
> allow multi-line short descriptions.
>
>
* Paul Elliott [130829 03:35]:
> Ok I will send you an example. [...]
> Tell me if this example is helpfull.
Yes, it is helpful. That seems to be a ugly effect of git wanting to
allow multi-line short descriptions.
As a workaround till this is fixedI suggest starting each commit with
a single li
* Paul Elliott [130822 04:15]:
> ++From: Paul Elliott
> ++Date: Wed, 21 Aug 2013 02:09:27 -0500
> ++Subject: =?UTF-8?q?harden=20library=20against=20buffer=20overflow=20attack?=
> ++ =?UTF-8?q?s=20on=20sprintf=0Acalls=20to=20sprintf=20with=20'%s'=20in=20fo?=
> ++ =?UTF-8?q?rmat=20string=20replaced
Package: git-dpm
Version: 0.8.4-1
Severity: normal
Dear Maintainer,
When ever I call git-dpm update-patches for a new patch,
the dep-3 headers on old patches get replaced with inferior
non dep-3 stuff.
Here is sample part of diff from such an update-patches
--
- Description:
5 matches
Mail list logo
