[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87mvk33b6p.fsf@miraculix.mork.no>
Date: Tue, 23 Aug 2016 14:46:22 +0200
From: Bjørn Mork <bjorn@...k.no>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: "Michael S. Tsirkin" <mst@...hat.com>,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
Jonathan Corbet <corbet@....net>,
virtualization@...ts.linux-foundation.org,
Julia Lawall <julia.lawall@...6.fr>
Subject: Re: [PATCH] CodingStyle: add some more error handling guidelines
Dan Carpenter <dan.carpenter@...cle.com> writes:
> Hike up the mountain, then if you get stuck hike back down using the
> exact same path.
OK, I understand what you say. I just can't resist objecting to that
example ;)
In my experience, finding the exact same path back after hiking up a
mountain is really hard. Especially if you are in enough trouble already
to get stuck. Up and down tend to look completely different. Looking
back all the time while you go up might help, but finding your way back
by simply taking the reverse path is definitely not easy.
Bjørn
Powered by blists - more mailing lists