On Sat, 30 Oct 2004 14:50:37 +0200, Torsten Curdt <tcurdt@apache.org> wrote:
> kfogel@collab.net wrote:
>
> >Erik Huelsmann <ehuels@gmail.com> writes:
> >
> >
> >>>But this means the pre commit hook
> >>>needs to change the transaction.
> >>>
> >>>Somewhere I read this is not (yet?)
> >>>possible.
> >>>
> >>>What's the status on that?
> >>>
> >>>
> >>It's not currently possible and not on any schedule to be addressed.
> >>Most Subversion developers feel that it's not ok for a server to
> >>change a committers contribution.
> >>
> >>
> >
> >To be dangerously accurate:
> >
> >It's *possible*, in that nothing (except the warning signs all over
> >pre-commit.tmpl) will stop you from doing it. But you shouldn't do
> >it, because the result in the committer's working copy would be
> >unpredictable.
> >
> >
> Ah ...sure ...that makes sense!
> Hope we can find a different way.
Well, you can set revprops without problems in a pre-commit hook (or
post-commit for that matter), because with the exception of svn:date
and svn:author, they are not stored in the clients working copy.
There is one problem with that scenario though: there (currently) is
no way to retrieve the value of revprops of a certain revision range.
(with the exception of svn:log ofcourse :-)
Bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 30 17:12:34 2004