On 08.11.2012 23:53, Greg Creager wrote:
> We use a tsvn:logtemplate at the root of all our branches/trunk to
> populate commit dialogs. We have a use case where we need to use a
> different logtemplate if a file is committed to a particular
> directory lower down the directory tree.
> mycomp/trunk -> normal log template mycomp/trunk/dir1/dir2/specialdir
> --> special log template
> I placed a logtemplate prop on the lower level 'special' dir and
> assumed it would be used if any file in the commit fell under this
> directory, but what I am finding is that the lower level logtemplate
> is ignored unless the commit takes place at or below that level (I
> would have to initiate the commit on 'specialdir', if I commit at
> trunk I get the higher level template).
> I would think the lower level template should take precedence
> shouldn't it?
Imagine something like this:
now, if all root, folder1 and folder2 have different properties set and
there are modified files in all folders and you commit from root: which
property should be used?
There's only one commit dialog, but it shows the files directly under
root, those in folder1 and those in folder2.
Because of that, the properties are used from the folder you commit from
upwards (direction to the working copy root) and not downwards.
> Ideas here? How can I get a message to the user if they are
> committing under the 'specialdir' area? We don't have server side
> hooks here. Is there a property that would fire as a client-side hook
> without the clients being setup for it?
You could use a nightly build from trunk: it has new project properties
that allow you to configure client-side hooks:
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-11-11 13:52:14 CET