From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] gmp: also generate the libgmpcxx library & package it properly
Date: Thu, 01 Dec 2011 16:57:58 +0000 [thread overview]
Message-ID: <1322758679.26081.242.camel@phil-desktop> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94E3D9E9B9@orsmsx504.amr.corp.intel.com>
On Tue, 2011-11-29 at 14:51 -0800, Kamble, Nitin A wrote:
> Thank you for the explanation. BTW where can I find official rules about signed-off-by line
The "Signed-off-by" idiom originated with the kernel people and
Documentation/SubmittingPatches in the linux source tree contains a
fairly good description of what it means to them.
I'm not sure that there are any official rules about its use in OE apart
from what's in the Commit Patch Message Guidelines (see the wiki).
p.
next prev parent reply other threads:[~2011-12-01 17:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 19:30 [PATCH 0/4] Misc recipe fixes nitin.a.kamble
2011-11-29 19:30 ` [PATCH 1/4] gmp: also generate the libgmpcxx library & package it properly nitin.a.kamble
2011-11-29 19:37 ` Otavio Salvador
2011-11-29 20:20 ` Phil Blundell
2011-11-29 21:08 ` Kamble, Nitin A
2011-11-29 21:12 ` Koen Kooi
2011-11-29 21:43 ` Kamble, Nitin A
2011-11-29 22:05 ` Phil Blundell
2011-11-29 22:51 ` Kamble, Nitin A
2011-12-01 16:57 ` Phil Blundell [this message]
2011-12-01 17:17 ` Richard Purdie
2011-12-01 17:26 ` Koen Kooi
2011-12-01 18:37 ` Joshua Lock
2011-12-01 19:29 ` Koen Kooi
2011-12-01 23:42 ` Philip Balister
2011-11-29 19:30 ` [PATCH 2/4] binutils: fix for .debug files QA warnings nitin.a.kamble
2011-11-29 19:30 ` [PATCH 3/4] libtool: Upgrade from 2.4 -> 2.4.2 nitin.a.kamble
2011-11-29 19:30 ` [PATCH 4/4] libx11-trip_1.4.4: fix the source tarall checksums nitin.a.kamble
2011-11-29 19:38 ` Otavio Salvador
2011-11-29 19:40 ` Kamble, Nitin A
2011-12-01 20:41 ` [PATCH 0/4] Misc recipe fixes Richard Purdie
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=1322758679.26081.242.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox