From: Holger Freyther <holger+oe@freyther.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Faking sign offs is bad
Date: Sun, 30 May 2010 09:30:15 +0800 [thread overview]
Message-ID: <4C01BFA7.5040800@freyther.de> (raw)
In-Reply-To: <AANLkTinPePxmIwOptgdFv-4CkJWzixbLvB26pxBw1dec@mail.gmail.com>
On 05/29/2010 07:14 PM, Andrea Adami wrote:
> The patch was sitting since long time (I had no time to test it
> before) and recently udev has been changed. I wanted to give it a bump
> before 'static' recipe renaming.
>
> I'm sorry if its signature not conform.
Hi,
first of all thank you for your contribution. The issue here is that a
"Signed-off-by:" is not to give credit but at least in the classic sense
gives the origin (route of the patch to the tree).
In case you want to give credit you can use it in the commit message,
lile this patch is based on work of... or if it is fully written by
someone else use the --author on git commit.
happy hacking
z
next prev parent reply other threads:[~2010-05-30 1:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 9:37 Faking sign offs is bad Koen Kooi
2010-05-29 10:58 ` Frans Meulenbroeks
2010-05-29 11:14 ` Andrea Adami
2010-05-30 1:30 ` Holger Freyther [this message]
2010-05-30 12:51 ` Broken recipes butters
2010-05-30 13:14 ` Dr. Michael Lauer
2010-05-30 13:23 ` butters
2010-05-29 11:15 ` Faking sign offs is bad Andrea Adami
2010-05-29 17:09 ` Andrea Adami
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=4C01BFA7.5040800@freyther.de \
--to=holger+oe@freyther.de \
--cc=openembedded-devel@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