On Mon, 2014-01-20 at 08:02 +0100, Julia Lawall wrote: > > > > $ time ./gentree.py --clean --verbose --test-cocci \ > > > > patches/collateral-evolutions/network/11-dev-pm-ops.cocci \ > > > > /home/mcgrof/linux-next/ \ > > > > /home/mcgrof/build/backports-20131206 > > > > I'm not really convinced that adding profile options for spatch is a > > good thing in gentree anyway. It's complicated enough as is, and running > > the spatch manually isn't all that difficult. If you use the --gitdebug > > option to gentree, you could even roll back to just before the patch was > > applied before running it manually. > I'm not sure to understand the issue. Spatch has a --profile option, but > I don't see it in the above code. From my point of view, it could be nice > if people are somehow encouraged to use that option from time to time, > because it increases the chance that they will report back on performance > problems. But there is no need for it to bein the default execution path. I'm just saying that making 'gentree' the kitchen sink of backports generation, spatch profiling, patch refreshing, etc. will just make for really messy code (it's not particularly clean as is) and that I don't see the need for adding everything into it since running spatch --profile or other such manually isn't terribly difficult (so there's little reason to add it to gentree.) johannes -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
