Re: Interactive Hooks

On Mon, Jun 15, 2009 at 10:15, David Weintraub<qazwart_at_gmail.com> wrote:
> As others have told you, it's not possible. The major issue is that the hook
> runs completely on the server and the only communication to the client is
> indicating a failure by the hook script doing an exit other than zero.
...
> What you really need to ask yourself is why do you need to ask a developer
> if they are sure whether or not they want to commit or add a particular
> file. Are developers modifying standard text based files and replacing them
> with non-text files? Are developers submitting unicode files instead of pure
> ascii files? What is your policy trying to prevent?

I'm looking at protecting some of us from our own careless actions.
For instance, adding a binary file inadvertently, when binary files
are not prevented but not wanted in all cases.

In other words, I would like to warn users that they are adding a
binary file, are they sure they want to do that?

Thanks for the info, David. I understand the downside here.

A solution would be for the repository manager to have the capability
to delete a specific file completely from the repository (but keep the
history of it happening). (That may be on the list of desired
enhancements.)

Regards,

-Tom

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2362315

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-16 01:32:15 CEST