Re: [PATCH] checkkconfigsymbols.py: make it Git aware

2015-03-14 Thread Valentin Rothberg
On Fri, Mar 13, 2015 at 9:20 PM, Paul Bolle wrote: > On Wed, 2015-03-11 at 16:04 +0100, Valentin Rothberg wrote: >> Paul, how long does your monster run? Maybe I just call it wrong or >> mess up with caches. > > Even longer, I presume. Because an update for just a new linux next > release can tak

Re: [PATCH] checkkconfigsymbols.py: make it Git aware

2015-03-13 Thread Paul Bolle
On Wed, 2015-03-11 at 16:04 +0100, Valentin Rothberg wrote: > Paul, how long does your monster run? Maybe I just call it wrong or > mess up with caches. Even longer, I presume. Because an update for just a new linux next release can take over a minute on my fastest machine (a ThinkPad X220). (Re

Re: [PATCH] checkkconfigsymbols.py: make it Git aware

2015-03-11 Thread Valentin Rothberg
It seems that using 'git cat-file blob commit:path' instead of 'git reset --hard commit' + open is much more expensive. The execution time jumps from 3 secs to 3 mins. Paul, how long does your monster run? Maybe I just call it wrong or mess up with caches. Kind regards, Valentin On Wed, Mar 1

Re: [PATCH] checkkconfigsymbols.py: make it Git aware

2015-03-11 Thread Valentin Rothberg
On Wed, Mar 11, 2015 at 3:19 PM, Valentin Rothberg wrote: > On Wed, Mar 11, 2015 at 1:04 PM, Paul Bolle wrote: >> On Wed, 2015-03-11 at 12:16 +0100, Valentin Rothberg wrote: >>> Note that both options require to 'git reset --hard' the user's Git >>> tree, which can lead to the loss of uncommitted

Re: [PATCH] checkkconfigsymbols.py: make it Git aware

2015-03-11 Thread Valentin Rothberg
On Wed, Mar 11, 2015 at 1:04 PM, Paul Bolle wrote: > On Wed, 2015-03-11 at 12:16 +0100, Valentin Rothberg wrote: >> Note that both options require to 'git reset --hard' the user's Git >> tree, which can lead to the loss of uncommitted data. > > My local "800 line perl monster" basically does >

Re: [PATCH] checkkconfigsymbols.py: make it Git aware

2015-03-11 Thread Paul Bolle
On Wed, 2015-03-11 at 12:16 +0100, Valentin Rothberg wrote: > Note that both options require to 'git reset --hard' the user's Git > tree, which can lead to the loss of uncommitted data. My local "800 line perl monster" basically does git ls-tree -r $commit_or_tag which allows you to generate

[PATCH] checkkconfigsymbols.py: make it Git aware

2015-03-11 Thread Valentin Rothberg
The script now supports to check a specified commit or a specified range of commits (i.e., commit1..commit2). Developers and maintainers are encouraged to use this functionality before sending or merging patches to avoid potential bugs. This patch adds the following options to the script: -c CO