From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel@lists.openembedded.org
Cc: Paul Menzel <paulepanter@users.sourceforge.net>
Subject: Re: [PATCH] eglibc-2.9: allow building with newer GNU make
Date: Wed, 14 Sep 2011 16:43:35 +0200 [thread overview]
Message-ID: <4E70BD97.4060401@dresearch-fe.de> (raw)
In-Reply-To: <1316010999.6686.108.camel@mattotaupa>
On 14.09.2011 16:36, Paul Menzel wrote:
>>>> The patch header is missing [1].
>>>
>>> Hmmm? After reading [1] i could not find what exactly is missing.
>>
>> Does the guidelines require that the patch files itself (make-3.82.patch in this case) need a header (in addition to the commit comment)?
>
> Yes, that is correct.
It would be very helpful if [1] could be modified in a way that makes clear that it talk about to separate things: the commit message *and* the patch header.
This was totally unclear for me after reading it.
>> If yes, how do i create such a header? Normally i create the patch with "diff -Nurd".
>>
>> If no, please enlighten me what is required?
>
> You can add any text to a diff file above a `---` I think. `patch` can
> handle that. But there should be some example in the repositories.
OK, i'll create a new version of the commit.
Steffen
[1] http://openembedded.org/index.php?title=Commit_Patch_Message_Guidelines
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2011-09-14 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 13:29 [PATCH] eglibc-2.9: allow building with newer GNU make Steffen Sledz
2011-09-13 14:51 ` Paul Menzel
2011-09-13 19:38 ` Steffen Sledz
2011-09-14 14:30 ` Steffen Sledz
2011-09-14 14:36 ` Paul Menzel
2011-09-14 14:43 ` Steffen Sledz [this message]
2011-09-14 14:58 ` Paul Menzel
2011-09-14 14:55 ` [PATCH v2] " Steffen Sledz
2011-09-15 9:08 ` Paul Menzel
2011-09-15 10:14 ` Steffen Sledz
2011-09-13 15:19 ` [PATCH] " Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E70BD97.4060401@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paulepanter@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.