From: Aleksey Kuleshov <rndfax@yandex.ru>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] ehci-hcd: remove useless timeout
Date: Fri, 04 Mar 2016 15:04:49 +0300 [thread overview]
Message-ID: <4943131457093089@web17h.yandex.ru> (raw)
In-Reply-To: <20160304145955.a02cc43b4d49ae2cc2897f97@gmail.com>
[quote]
To improve tracking of who did what, especially with patches that can
percolate to their final resting place in the kernel through several
layers of maintainers, we've introduced a "sign-off" procedure on
patches that are being emailed around.
[/quote]
So Linux kernel had some problems due to their huge developers/maintainers list
and they solved them by using "sign-off" procedure.
Do Barebox have that burden of "patches that can
percolate to their final resting place in the kernel through several
layers of maintainers"?
Also in chapter 11 there are rules which are pure bureaucratic.
Bureaucracy is a thing of a large projects.
Is Barebox such as big as Linux that it must have these rules too?
Solving inexisting problems doesn't make life easier but complicates it.
So, the question "what this (git commit -s) will give you?" is still open.
04.03.2016, 14:33, "Antony Pavlov" <antonynpavlov@gmail.com>:
> On Fri, 04 Mar 2016 13:42:14 +0300
> Aleksey Kuleshov <rndfax@yandex.ru> wrote:
>
>> Don't get me wrong, but what this (git commit -s) will give you?
>> What is the purpose of this?
>
> You can find the answer at https://www.kernel.org/doc/Documentation/SubmittingPatches
> Please see chapter 11 (Sign your work).
>
>> 04.03.2016, 10:11, "Sascha Hauer" <s.hauer@pengutronix.de>:
>>
>> > Also, like you other patches this one lacks a SoB. Please commit with
>> > git commit -s.
>
> --
> --
> Best regards,
> Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-03-04 12:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 12:48 Aleksey Kuleshov
2016-03-04 7:11 ` Sascha Hauer
2016-03-04 10:42 ` Aleksey Kuleshov
2016-03-04 11:59 ` Antony Pavlov
2016-03-04 12:04 ` Aleksey Kuleshov [this message]
2016-03-04 13:59 ` Antony Pavlov
2016-03-04 15:03 ` Aleksey Kuleshov
2016-03-04 17:58 ` Andrey Smirnov
2016-03-04 20:47 ` Aleksey Kuleshov
2016-03-04 22:57 ` Andrey Smirnov
2016-03-05 0:04 ` Aleksey Kuleshov
2016-03-05 9:15 ` Antony Pavlov
2016-03-05 9:27 ` Aleksey Kuleshov
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=4943131457093089@web17h.yandex.ru \
--to=rndfax@yandex.ru \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.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