From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] Pull request: u-boot-staging
Date: Wed, 23 Nov 2011 18:26:51 +0200 [thread overview]
Message-ID: <4ECD1ECB.40407@compulab.co.il> (raw)
In-Reply-To: <20111123160158.40F501FFB395@gemini.denx.de>
Hi Wolfgang, Stefano,
On 11/23/11 18:01, Wolfgang Denk wrote:
> Dear Igor Grinberg,
>
> In message <4ECCB840.9050700@compulab.co.il> you wrote:
>>
>>> Because I am not the author of the patches, I do not add my Signed-off,
>>> and I do the same for u-boot-imx, where I am the custodian. As far as I
>>> know, all custodians are doing in the same way.
>>
>> I see... Is there a U-Boot policy regarding this somewhere?
>
> Nobody bothered yet to write down such a thing, so we all go on as we
> started some time in the past.
>
>> Because in Linux every person involved in pushing patches
>> should add an SOB to the commit message.
>
> The question is how you define "pushing".
> "Documentation/SubmittingPatches" says:
>
> | By making a contribution to this project, I certify that:
> |
> | (a) The contribution was created in whole or in part by me and I
> | have the right to submit it under the open source license
> | indicated in the file; or
> |
> | (b) The contribution is based upon previous work that, to the best
> | of my knowledge, is covered under an appropriate open source
> | license and I have the right under that license to submit that
> | work with modifications, whether created in whole or in part
> | by me, under the same open source license (unless I am
> | permitted to submit under a different license), as indicated
> | in the file; or
> |
> | (c) The contribution was provided directly to me by some other
> | person who certified (a), (b) or (c) and I have not modified
> | it.
> |
> | (d) I understand and agree that this project and the contribution
> | are public and that a record of the contribution (including all
> | personal information I submit with it, including my sign-off) is
> | maintained indefinitely and may be redistributed consistent with
> | this project or the open source license(s) involved.
> |
> | then you just add a line saying
> |
> | Signed-off-by: Random J Developer <random@developer.example.org>
>
> (a) and (b) don't apply here, and (d) is not relevant in this context.
> So the question is if (c) applies, or not.
Well, I think yes (c) applies here and if you look into the Linux
git log, you will see that all patches applied by maintainers are
also signed by them.
>
>
> My personal point of view is that someone who just applies a patch
> (without any changes) from the mailing list or from PatchWork does not
> have to sign it.
This is perfectly fine. Should we have this written somewhere?
Or should we adopt the Linux version of SubmittingPatches in regard
to signing commits?
>
> If it were the other way round, I would have a problem for example
> when I use "git pull" or "git merge" to apply commits from a
> custodian's repository - neither "git pull" nor "git merge" provide
> ways to sign such an action - not to mention that then I would have to
> sign all included commits, too.
Right, and that is not done also in Linux - when Linus Torvalds pulls
stuff in, he *does not* sign it as well, because (c) *does not* apply
in this case, so you will _not_ have a problem.
>
>
> But maybe I'm just misinterpreting...
Well, if (c) really does not apply here, then probably you are
misinterpreting...
--
Regards,
Igor.
next prev parent reply other threads:[~2011-11-23 16:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 8:58 [U-Boot] [GIT PULL] Pull request: u-boot-staging Stefano Babic
2011-11-21 21:10 ` Wolfgang Denk
2011-11-22 5:06 ` Simon Glass
2011-11-22 7:18 ` Stefano Babic
2011-11-22 8:59 ` Stefano Babic
2011-11-22 22:28 ` Wolfgang Denk
[not found] ` <4ECC9D3F.2080100@compulab.co.il>
2011-11-23 8:16 ` Stefano Babic
2011-11-23 9:09 ` Igor Grinberg
2011-11-23 16:01 ` Wolfgang Denk
2011-11-23 16:26 ` Igor Grinberg [this message]
2011-11-23 16:57 ` Stefano Babic
2011-11-23 17:08 ` Andy Fleming
2011-11-23 20:14 ` Wolfgang Denk
2011-11-24 6:57 ` Igor Grinberg
2011-11-24 11:51 ` Wolfgang Denk
2011-11-24 12:15 ` Igor Grinberg
2011-11-23 20:12 ` Wolfgang Denk
2011-11-24 6:48 ` Igor Grinberg
2011-11-24 7:02 ` Graeme Russ
2011-11-24 7:24 ` Igor Grinberg
2011-11-24 11:53 ` Wolfgang Denk
2011-11-24 11:46 ` Wolfgang Denk
2011-11-24 12:33 ` Igor Grinberg
2011-11-28 18:52 ` Wolfgang Denk
2011-11-29 7:34 ` Igor Grinberg
-- strict thread matches above, loose matches on Subject: below --
2011-11-23 7:37 Heiko Schocher
2011-11-23 20:26 ` Wolfgang Denk
2011-12-09 13:50 [U-Boot] [GIT PULL] Pull request u-boot-staging Stefano Babic
2011-12-10 21:43 ` Wolfgang Denk
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=4ECD1ECB.40407@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=u-boot@lists.denx.de \
/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