From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] Pull request: u-boot-staging
Date: Thu, 24 Nov 2011 09:24:42 +0200 [thread overview]
Message-ID: <4ECDF13A.8040002@compulab.co.il> (raw)
In-Reply-To: <CALButCLDGEiC9vVnnXg0vC60SU=wizQtCX_pGPYfkLoPEYkKLQ@mail.gmail.com>
Hi Graeme,
On 11/24/11 09:02, Graeme Russ wrote:
>
> On Nov 24, 2011 5:48 PM, "Igor Grinberg" <grinberg at compulab.co.il <mailto:grinberg@compulab.co.il>> wrote:
>>
>> On 11/23/11 22:12, Wolfgang Denk wrote:
>> > Dear Stefano Babic,
>> >
>> > In message <4ECD25EA.1020508 at denx.de <mailto:4ECD25EA.1020508@denx.de>> you wrote:
>> >>
>> >>>> | (c) The contribution was provided directly to me by some other
>> >>>> | person who certified (a), (b) or (c) and I have not modified
>> >>>> | it.
>> > ...
>> >>>> (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.
>> >>
>> >> Reading (c), I can interprete as Igor does...
>> >
>> > I _can_ interpret that so as well, but does it make sense?
>> >
>> > By that logic _all_ commits in the Linux kernel must have the SoB of
>> > Linus Torvalds. Do they?
>>
>> No they should not.
>> As for my understanding, the delivery path ends with the repository
>> from which the pull process starts.
>> That is, the repository that has the *commit id* first set
>> and then it is not changed, because pull requests keep the
>> history intact. This is the reason, why Linus Torvalds do not
>> sign each patch pulled from others with git pull.
>>
>
> Isn't the committer field enough?
Sometimes, it can be useful to see a part of the delivery path,
but as I've said in my other reply in this thread, it is a meter
of choice.
>
> And what difference does it really make anyway?
No functional difference... that's for sure.
It is more like how we want things to be done.
--
Regards,
Igor.
next prev parent reply other threads:[~2011-11-24 7:24 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
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 [this message]
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=4ECDF13A.8040002@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 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.