Aaron Schrab writes:
> At 18:01 -0800 28 Dec 2012, Junio C Hamano wrote:
>>Will it be "all-or-none", or "I'll allow these but not those"?
>
> Currently it just uses the exit code to communicate that back, so it's
> all-or-none. I think I'll keep that in the updated version as well.
Thanks; tha
At 18:01 -0800 28 Dec 2012, Junio C Hamano wrote:
One lesson we learned long time ago while doing hooks is to avoid
unbound number of command line arguments and instead feed them from
the standard input. I think this should do the same.
Good point. I had been trying to keep the interface for
Aaron Schrab writes:
> There have been at least a couple of submissions to add support for a
> pre-push hook, which were rejected at least partially because they didn't
> provide enough information to a hook script for it to determine what was
> to be pushed any better than a separate wrapper aro
There have been at least a couple of submissions to add support for a
pre-push hook, which were rejected at least partially because they didn't
provide enough information to a hook script for it to determine what was
to be pushed any better than a separate wrapper around the 'git push'
command woul
4 matches
Mail list logo
