On Wed, Feb 01, 2012 at 03:32:26PM -0500, Josh Boyer wrote:
>
> So I would be torn and lean away from it until the speed improves. I know
> if this makes it to RHEL people would complain and it would get ripped out
> in favor of the old way.
If we're going on pure speed then sure. There's no reason to replace
what is working today with something that is much slower. What I'm more
interested in though, is either:
1) Does the additional verification from merge_config.sh prove useful
enough to warrant a slowdown? I can see it being useful to make sure we
don't screw something up on a rebase, etc.
Sure. I'll agree with that.
2) Can merge.pl be adapted to produce similar output without making it
much slower?
If I have to go with 2, I'll be replacing merge.pl with merge.py because
I don't speak perl. ;)
It shouldn't be too hard if given to someone who knows python. That is
probably worth pursuing upstream.
Cheers,
Don