[SVN-3028] Always exclude given paths during commit (and possibly update)

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: ---
• Fix Version/s: blue-sky
• Component/s: cmdline client
• Assignee: Unassigned
• Reporter: Subversion Importer
• Created: 22/Nov/07 10:53
• Updated: 27/Oct/18 16:28
• Resolved: 18/Aug/11 21:53

Description

From the FAQ: "I have a file in my project that every developer must change, but
I don't want those local mods to ever be committed. How can I make 'svn commit'
ignore the file?"

The suggested solution is to use platform specific scripts to "initialize" the
working copy/checkout.

This is however platform specific and requires maintenance effort.

This is also impractical for a large number of files which are not to be checked in.

For example we have a complete Eclipse instance in our svn repository and we
want to ignore every change in its directory and below. Because Eclipse more or
less at random creates and deletes file from its own directory we have no way of
knowing which individual files may be change or deleted by starting Eclipse.

To avoid that an update creates files again that were deleted by running Eclipse
the ignore setting I am asking for should also apply to updates. (The latter
might possibly have to be optional.)

Also, when the user forgets to run the init script after a checkout (and
possibly after an update, which might add further files that must be renamed for
things work properly) applications might misbehave when they do not find their
expected files.

All these efforts and concerns would be solved by an ignore functionality that
applies to checkout and commit as well, as described above.

Original issue reported by canhuth

Issue Links

• duplicates: SVN-2858 Support file property which indicates that commit must be manually forced
• is duplicated by: SVN-3415 svn cmdline client should honor the ignore-on-commit changelist