Re: [Locking] Quick question about adding lock/unlock support to mailer.py

"Brian W. Fitzpatrick" <fitz@collab.net> writes:

> If we're passing paths to mailer.py through STDIN (which is how
> locked/unlocked paths are passed to post-(un)lock), is it OK to pass
> them to mailer.py through STDIN? If so, do I just document that you
> can't pass config options to mailer.py through STDIN (by using '-')
> when calling lock or unlock?

I'd like to just kill the whole stupid option (the ability to read
config from stdin). I added it thinking I'd need it for something,
and never used it. I seriously doubt folks are actually using that
feature.

But if we want to maintain compat, then yes, we could document that
'-' doesn't work for lock/unlock.

Alternatively, you could make mailer.py take an option to read the
lock/unlock paths from a file (though that might be too burdensome for
hook scripts, having to create a unique tmpfile and clean it up).

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 17 00:08:19 2005