Managing user specific files

[Christian Bang <pi...@laposte.net>]

Hi,

some projects require files that derive from a common template to which
each user makes his local changes (which he won't/shouldn't commit).
When the template was changed and committed, these changes will be
merged to each user when he updates his working copy. In some cases this
is not a desired behavior since it will overwrite the local changes.

My work around: create a <file>.template.
Disadvantage: after a checkout  one needs to copy all instances of
<file>.template to <file>.

Is there a better way to solve the problem?

Why doesn't one define a new property "svn:no-update"? Each file with
this flag would be checked out but not updated. However a diff between
the working copy and the repository would show the differences. Maybe a
flag like --force would force the update/merge.
This could be a possible Subversion enhancement, don't you think?

Best regards,
Christian

PS: Please answer also to my email address since I'm not on the mailing
list.

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