Jeff King wrote:
>On Fri, Sep 12, 2008 at 05:54:27PM +0200, Stephen R. van den Berg wrote:
>> True. But repopulating this cache after cloning means that you have to
>> calculate the patch-id of *every* commit in the repository. It sounds
>> like something to avoid, but maybe I'm overly concerned, I have only a
>> vague idea on how computationally intensive this is.
>For a rough estimate, try:
> time git log -p | git patch-id >/dev/null
On my system that results in 2ms per commit on average. Not huge, but
not small either, I guess. Running it results in real waiting time, it
all depends on how patient the user is.
--
Sincerely,
Stephen R. van den Berg.
"Father's Day: Nine months before Mother's Day."
--
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
