Robin Rosenberg wrote:
Since the sleep is per invocation of cvsexportcommit it won't hurt
too much since it is rarely invoked on a huge number of git commits.
The question also is, why does this happen on two sequential invocations of cvsexportcommit, but not on two cvs commits done by cvsexportcommit? This should look the same to cvs, no?
I reread my post here... My last sentence was a comment to the patch
and not the sleep in CVS.
Yes, I realize this. Still, I wonder the same: why is this needed *per invocation of cvsexportcommit* and not *per invocation of cvs*? Seems unintuitive to me, or I didn't read the patch good enough.
cheers
simon
--
Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\
Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
