On Sat, Dec 5, 2009 at 2:45 PM, Oswald Buddenhagen <o...@kde.org> wrote: > 3) this is subject to connectivity problems. while the post-receive > thing could kinda work if complete atomic ref snapshots are queued, it > is a non-starter for a pre-receive hook (which needs to be called in > real-time).
To be honest, I'm quite hesitant to adding any pre-receive hooks that does any kind of non-trivial work. See, if pushing is slow due to that hook people won't complain about the hook, they'll complain, to me, that Gitorious is slow. That, and managing resources in a asynchronous setup is far easier (I can run it on other machines if it's too heavy). So I'd think hard and long about whether that hook really is essential at that particular point in your workflow? JS _______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest
