From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot git usage model
Date: Mon, 15 Oct 2012 15:42:23 -0600 [thread overview]
Message-ID: <507C833F.30409@wwwdotorg.org> (raw)
In-Reply-To: <20121015185524.965702029CD@gemini.denx.de>
On 10/15/2012 12:55 PM, Wolfgang Denk wrote:
> Dear Stephen Warren,
>
> In message <507C3AA4.6050707@wwwdotorg.org> you wrote:
>>
>> Irrespective of the documentation (which I obviously read the way I
>> describe anyway...), the kernel practice is that everyone who writes or
>> commits a patch adds their S-o-b line, and everyone who simply merges a
>
> I'm aware of this.
>
>> branch from someone else checks that the provider of the branch added
>> their S-o-b to patches they applied (rather than merged themselves) but
>> does not add their own S-o-b (because it's impossible).
>
> Is such checking really taking place? Are there any tools to support
> this?
I've certainly seen people give feedback on patches that the appropriate
S-o-b lines aren't present. I don't recall if I've explicitly seen
anyone called out for not doing this during a merge (which most likely
means there was never an issue, not that people weren't checking), so I
can't say for 100% certain that everyone is doing this, but they
certainly should be.
git log is probably what I would use to validate this.
next prev parent reply other threads:[~2012-10-15 21:42 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
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 [this message]
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=507C833F.30409@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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