Re: Client-side commit hooks (Revisited)

On Friday 02 August 2002 13:10, Karl Fogel wrote:
> No. But you could refer to the code-change revision in the log
> message of your bug-tracker-change revision.

Okay, I guess I'll just have to create separate revisions.

> (Not all projects will want to store their bug db in the same
> repository as their code, anyway, I would guess).

The question then is, how does a hook figure out the user/pass in order to
connect to a separate repository? Maybe some magic will be required in the
hook's configuration (ie., don't support arbitrary URLs, only ones that have
been pre-configured and their passwords stored in the config).

Thanks for your help. Things are a lot clearer in my head now, even though it
won't be quite as slick as I had hoped.

-- 
Peter Davis
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org