Wouldn't it work at least as well to put this info in the commit message in a
format you could check with a regexp in a pre-commit hook? Then you'd see it in
the history log.
David Weintraub wrote:
> Thanks!
>
> That's all I have to know. It is possible to set revprops when doing a
> commit, so I should have a mechanism to check for those when doing a
> commit too.
>
> I thought that 1.5 allowed it, but I didn't know how.
>
> On Tue, Jun 22, 2010 at 1:15 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
>> There is 'svn commit --with-revprop' in >=1.5, does that help?
>>
>> David Weintraub wrote on Tue, 22 Jun 2010 at 07:36 -0000:
>>> I know this sounds strange, but can you set a revision property before
>>> a revision is created?
>>>
>>> For example, I make some file changes, and want to mark that my
>>> changes fixed bug # 1001. To do this, I'll set a revision property
>>> "corp:bugbix" to "1001". Then, I'll check in my changes with the new
>>> revision property.
>>>
>>> There are several revision properties that are set before the revision
>>> is committed: svn:log, svn:date, and svn:author. However, these are
>>> special revision properties used by Subversion. I'd like to have a
>>> pre-commit trigger to force users to set a particular custom revision
>>> property before checking in their code.
>>>
>>> I know older versions of Subversion could not do this, but I thought
>>> 1.5 or 1.6 could.
>>>
>>> Just working on a new pre-commit trigger, and want to know if this is
>>> something I can do.
>>>
>>>
>
>
>
Received on 2010-06-22 14:27:10 CEST