Can we avoid whitespace-only changes?
They increase effort to keeping up with what's been committed without adding
any value, and I find it takes twice as long to search them to find out what,
if anything, they functionally change.
I literally have to read it a second time to figure out that
Is this a regression? You previously didn't copy fowsr.sh and pwsweather.sh
... is this a new script? You're deleting 3 lines but adding a combined copy of
5... 3 of which were previously there.
-Philip
On 3/8/12 9:24 PM, openwrt-comm...@openwrt.org wrote:
Author: swalker
Date: 2012-03-09
On 9 March 2012 23:19, Philip Prindeville
philipp_s...@redfish-solutions.com wrote:
Can we avoid whitespace-only changes?
Not if it's the upstream code that has the whitespace changes (and
thus patches need to be updated/rebased so that they apply again, like
in this very commit).
Regards,
Hi Tatha,
sorry for answering so late I am currently very busy.
If I set CONFIG_BCMA_SFLASH=y and CONFIG_BCMA_NFLASH=y in the kernel
config, which I want to do for the default image in OpenWrt the image
will not work on by device with serial flash any more because
bus-drv_cc.flash_type will
