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 18:03:45 +0300 [thread overview]
Message-ID: <5405981457103825@web21g.yandex.ru> (raw)
In-Reply-To: <20160304165904.ca1b14a860e6fdb84a4a6e4f@gmail.com>
> https://github.com/maximeh/buildroot/tree/master/board/calao/qil-a9260/patches/barebox
>
> It is reasonable to have as much author(s) information as possible. So your Sob will be
> very usable if somebody who works with the patch.
This patch has "From:" field and exactly the same "Signed-off-by:" field.
So no new additional information Sob gives you here.
The Sob indeed will give you simplification when you want to squash many-many commits
by many-many authors and for god's sake you don't want to reclaim ownership of each commit!
But again, does Barebox facing such cases?
Does it really necessary to follow all linux-related work process rules? Just look at this:
Signed-off-by: James Hogan <james.hogan@imgtec.com>
Fixes: e9de688dac65 ("irqchip: mips-gic: Support local interrupts")
Cc: Andrew Bresticker <abrestic@chromium.org>
Cc: Qais Yousef <qais.yousef@imgtec.com>
Cc: Paul Burton <paul.burton@imgtec.com>
Cc: Jason Cooper <jason@lakedaemon.net>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-mips@linux-mips.org
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
Patchwork: https://patchwork.linux-mips.org/patch/9081/
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
That's something! Because many people are invlolved. Linux is a huge machine.
Barebox is not Linux.
And just for comparsion, this is from Barebox:
--------------------------
commit a6f73ec52f5c794938aa14b1264375228890f12c
Author: Ulrich Ölmann <u.oelmann@pengutronix.de>
Date: Thu Feb 4 08:25:24 2016 +0100
docs: fix typos
Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
diff --git a/Documentation/devicetree/bindings/barebox/barebox,state.rst b/Documentation/devicetree/bindings/barebox/barebox,state.rst
index d1b0627..d507657 100644
--- a/Documentation/devicetree/bindings/barebox/barebox,state.rst
+++ b/Documentation/devicetree/bindings/barebox/barebox,state.rst
@@ -43,7 +43,7 @@ Variable nodes
These are subnodes of a state node each describing a single
variable. The node name may end with ``@<ADDRESS>``, but the suffix is
-sripped from the variable name.
+stripped from the variable name.
State variables have a type. Currenty supported types are: ``uint8``,
``uint32``, ``enum32``, ``mac`` address or ``string``. Variable length
--------------------------
> Here is a poor example: patch without any comments at all, it's very difficult to trace origins
> of this patch:
>
> https://github.com/openwrt/openwrt/blob/master/target/linux/ar71xx/patches-4.4/200-MIPS-ath79-fix-ar933x-wmac-reset.patch
Indeed, plain patches lacks origins.
1) That's why everyone here uses "git send-email" so that "git am"
will apply patch with proper "Author:" field.
2) In the case of openwrt patch, why do anyone needs the origins anyway?
If this patch breaks something - fix with new one, if not - okay then.
If you know that that patch was written by Some Person - what this will give you?
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-03-04 15:04 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
2016-03-04 13:59 ` Antony Pavlov
2016-03-04 15:03 ` Aleksey Kuleshov [this message]
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=5405981457103825@web21g.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