Jay Levitt wrote:
>> So, if I've got this right, you add the svn:template property after
>> creating the template, adding it, and committing it to the
>> repository. However, if you want to modify the template, you remove
>> the property, commit its removal (requiring a special hack to detect
>> this case?), make your changes + restore the prop, and commit again.
>> This makes the editing process awfully clunky...
> Nonono, that would indeed be horrible.
> I'm envisioning this behaviour:
> - At some point after adding a file, somebody adds property
> "svn:template" to the file.
> - blame, cat, cleanup, copy, delete, info, list, lock, log, merge,
> prop*, resolved, revert, unlock are unaffected by svn:template.
> - status and update ignore the file, as if it were in its parent's
> svn:ignore property.
> - diff ignores the file if you are diffing its directory, but displays
> the changes if you are diffing it directly.
> - commit will, by default, ignore the file.
> - If you pass --commit-updated-template to commit, it will check your
> local changes in.
> How's that sound?
Have you seen http://subversion.tigris.org/issues/show_bug.cgi?id=2858 ?
C. Michael Pilato <firstname.lastname@example.org>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Tue Sep 4 18:29:35 2007