From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot git usage model
Date: Mon, 15 Oct 2012 10:56:07 -0700 [thread overview]
Message-ID: <507C4E37.8000000@ti.com> (raw)
In-Reply-To: <20121013222545.DBD13203AF9@gemini.denx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/13/12 15:25, Wolfgang Denk wrote:
> Dear Tom,
>
> In message <5079D95E.4070609@ti.com> you wrote:
>>
>> While also IANAL (and I try and stay out of these discussions),
>> paging around in the kernel log it sure seems like Linus and
>> akpm both add S-O-B when they git am something in (perhaps why
>> there is git am --signoff?) but not when it comes via pull
>> request. In other words, up until the point it goes into
>> intended-to-be-pulled-somehow-someway git, whomever is
>> presenting the work adds one (or more) to say I (we) worked on it
>> and yes, applies as well as the person bringing it in (I touch
>> this and believe it to be).
>
> Yes, git am has such an option. But git fetch (or pull) does not.
> I see no technical difference if someone provides me a patch as
> such, or in form of a git repository with this patch applied so I
> can just "git fetch" from it. In both cases the result would be
> exactly the same: I add the patch to my local repository. But in
> one case I am supposed to sign it (and tools offer me options to
> do so), but in the other case I cannot do that, even if I wanted?
I will not claim the kernel practice to be 100% consistent, but yes.
git am --signoff, git pull/merge and no -s in merge commits seems to
be the practice. Perhaps we should stop saying we follow the kernel
process, link to it as useful background, but then document what we
actually want / do which is only require new S-O-B on code
modification, and allow custodians to add their own they want for
tracking or otherwise ease of not having to remember a different
workflow for kernel vs U-Boot?
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQIcBAEBAgAGBQJQfE43AAoJENk4IS6UOR1WKEUP/i2Ez8T+zv872jq6hjuhGhiE
xCdrc2+npXHx/DguOkHIQqFRPQwlKaAbaGgNLXFWdIHipUcuZlUI1sraLDiQJ0un
fToNRqlts0N/nXgwOMMBn13/aihSiGrOy6MvYB0RhFLZ5FVBXxdY3QXc6rOfFrom
45A+60T4VUmghyuoa3I5Oc+H9PEyvPG6BgVFm5JtwB6oPi7KypNOx0pSnv5z7uJ8
JkiLeWDlXag4VJyXFLbf2xOQRFgbFX8EgQcRXOWDjXet1lzXjP5sA9qVnYFMVFHJ
AANtj9XFpQft6CK1Wfyq2+9fVNoqQtdqmvjhNbuqJK1vehZrpL4//tO4O++eynnP
NlYxtSUDFLeWC/qyksdda02V5Gwme7pA3aMGUFU+VBgPrzAV2aCaseiOxKND//ni
MSX+KkBUHy0l8kV7TnwuZtIV+fEvvOkYLD3KMzYxa98h7hbMpUIEa8Ldhkjyw3qx
GrzEQ59xHV6stE2/nw++J30rzlxMrnavUU6ato25GcpSDIH2yPzDargrIBtDSteP
tHFLfsj8buHx8csylaecHc+qlICA8JshbMcYkYQpzOIKYI+6M6sJOWFeXY9xrIdg
b3zjZeJk6MRhU7cdv+q1JfPxmgXKrJ/51taimYJWH1b3saZXS4fEHhshPvbhZ5Sq
5PFd5XVPr+IkrvBKSfFT
=5YMo
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-10-15 17:56 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 18:49 [U-Boot] [PULL] u-boot-usb/next Marek Vasut
2012-10-09 14:23 ` Tom Rini
2012-10-09 21:03 ` [U-Boot] U-Boot git usage model (was: Re: [PULL] u-boot-usb/next) Stephen Warren
2012-10-09 21:32 ` Tom Rini
2012-10-09 22:14 ` [U-Boot] U-Boot git usage model Stephen Warren
2012-10-09 22:43 ` Albert ARIBAUD
2012-10-09 23:02 ` Graeme Russ
2012-10-09 22:59 ` Tom Rini
2012-10-09 23:07 ` Stephen Warren
2012-10-09 23:17 ` Graeme Russ
2012-10-09 23:00 ` Scott Wood
2012-10-09 23:25 ` Stephen Warren
2012-10-10 0:20 ` Scott Wood
2012-10-10 15:55 ` Stephen Warren
2012-10-10 22:02 ` Scott Wood
2012-10-10 22:19 ` Stephen Warren
2012-10-11 7:19 ` Wolfgang Denk
2012-10-11 11:53 ` Jason Cooper
2012-10-11 17:00 ` Stephen Warren
2012-10-13 19:08 ` Wolfgang Denk
2012-10-11 16:27 ` Albert ARIBAUD
2012-10-11 7:28 ` Wolfgang Denk
2012-10-11 16:54 ` Stephen Warren
2012-10-13 18:58 ` Wolfgang Denk
2012-10-09 22:19 ` [U-Boot] U-Boot git usage model (was: Re: [PULL] u-boot-usb/next) Albert ARIBAUD
2012-10-09 23:04 ` [U-Boot] U-Boot git usage model Stephen Warren
2012-10-10 6:15 ` Albert ARIBAUD
2012-10-10 16:04 ` Stephen Warren
2012-10-10 18:40 ` Albert ARIBAUD
2012-10-11 16:54 ` Scott Wood
2012-10-11 17:16 ` Albert ARIBAUD
2012-10-11 17:26 ` Stephen Warren
2012-10-11 18:30 ` Albert ARIBAUD
2012-10-13 19:30 ` Wolfgang Denk
2012-10-13 21:13 ` Tom Rini
2012-10-13 22:25 ` Wolfgang Denk
2012-10-15 17:56 ` Tom Rini [this message]
2012-10-15 19:00 ` Wolfgang Denk
2012-10-13 19:17 ` Wolfgang Denk
2012-10-15 16:32 ` Stephen Warren
2012-10-15 18:55 ` Wolfgang Denk
2012-10-15 21:42 ` Stephen Warren
2012-10-11 18:13 ` Scott Wood
2012-10-11 18:45 ` Albert ARIBAUD
2012-10-11 18:59 ` Scott Wood
2012-10-12 10:11 ` Albert ARIBAUD
2012-10-12 21:49 ` Scott Wood
2012-10-13 19:20 ` Wolfgang Denk
2012-10-13 19:06 ` Wolfgang Denk
2012-10-11 7:17 ` Wolfgang Denk
2012-10-11 16:38 ` [U-Boot] U-Boot git usage model (was: Re: [PULL] u-boot-usb/next) Tom Rini
2012-10-11 17:16 ` Scott Wood
2012-10-11 17:22 ` [U-Boot] U-Boot git usage model Stephen Warren
2012-10-11 17:27 ` Tom Rini
2012-10-11 18:30 ` Scott Wood
2012-10-12 5:29 ` Stefan Roese
2012-10-12 15:49 ` Tom Rini
2012-10-13 19:34 ` 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=507C4E37.8000000@ti.com \
--to=trini@ti.com \
--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.