> On 9 Mar 2012, Timothy Pearson stated: >> Not quite. I recognized some problems in GIT that could cause issues, >> so >> I wrote "babysitting" software that constantly combs through the GIT >> tree, >> making sure that all submodule references are up to date with the latest >> code and similar housekeeping tasks. That babysitting software can and >> does trigger commits to the tree, and it is these fixup commits that are >> taking a long time to carry out. > > Looks like that needs a bit of optimization. I can have a look at it and > see if there's a faster way to do the same thing, if you like. (And if > the code is publically visible.) > > -- > NULL && (void) 99% of the time is spent waiting for GIT to return from these commands: 'git pull' 'git reset --hard HEAD' 'git commit -a' That last one especially eats up a lot of resources, but I have found no other way to commit changes to a submodule reference to the parent tree. Tim