From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] BOOT_DELAY broken
Date: Mon, 13 Jun 2016 08:19:59 +0200 [thread overview]
Message-ID: <20160613061959.855C0101762@atlas.denx.de> (raw)
In-Reply-To: <alpine.LFD.2.20.1606121324330.17506@maverick.koi8.net>
Dear Sergey,
In message <alpine.LFD.2.20.1606121324330.17506@maverick.koi8.net> you wrote:
> OK, it is broken in last commit. Totally broken.
So what? Shit happens. Calm down, it's only ones and zeroes.
> I do NOT have time chasing this -- I'm in firefighting mode now with 14
> hours workdays because of this Tuesday deadline -- but guys, WTF!?
Nobody asked you to fix that. And that deadline thing is your
problem, not ours, right? So please don't offload your frustration
and stress to others.
> I could understand somebody submitting such a stupid patch affecting
> _HUNDREDS_ of boards without thinking of consequences but why had it
> been accepted and applied to uboot-master right away? There are other
> things that are broken and won't compile but trivial one-line patches
> fixing that breakage are silently ignored but such a enormous screwup
> leaving holes all over is accepted right away without any checking...
Who says "without checking"? As far as I know this patch has passed
buildman compile tests, plus runtime tests on all boards available to
the poster (which is more than the average developer has).
> Please do _NOT_ make such things any more. And if you do care please
> take my vehement NACK to this entire thing. I suggest it would be better
> to rollback that patch in its entirety -- there is too much work to fix
> the damage and there is absolutely no reason for this change at all in
> the first place.
Wrong approach. If there are such obscure dependencies in U-Boot code
they SHOULD be cleaned up. And yes, this can - and will -
occasionally cause temporary breakage, sometimes even in a large
scale. But bugs are for fixing. Bad code needs to be improved, not
to be conservated and never touched. I strongly recommend to sort out
the remaining issues and fix the problems instead of ignoring them.
Papering over known issues has never been a clever idea.
> Sorry for ranting but I simply could not stand it...
I can understand your frustration, especially when working under
stress. But eventually you may want to re-read your posting, think
about the tone which sounds extremely aggressive and insulting to me,
and then - maybe? - apologize to Heiko?
Thanks.
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Monday is an awful way to spend one seventh of your life.
prev parent reply other threads:[~2016-06-13 6:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 21:19 [U-Boot] BOOT_DELAY broken Sergey Kubushyn
2016-06-12 22:07 ` Ladislav Michl
2016-06-13 6:19 ` Wolfgang Denk [this message]
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=20160613061959.855C0101762@atlas.denx.de \
--to=wd@denx.de \
--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