Jack Bates wrote:
> I understand the svn:ignore property currently doesn't apply to
> resources already under version control, but our project is in this
> common situation: http://subversion.tigris.org/faq.html#ignore-commit
> We've worked around it, as suggested, by creating a "databases.yml.tmpl"
> file and removing "databases.yml" from version control, but I can't
> figure out for what reason the svn:ignore property shouldn't apply to
> version controlled resources?
In a sense, it does. svn:ignore is defined to be a collection of patterns
for files which should not be added to version control. And sure enough,
Subversion will not add to version control any
already-added-to-version-control files that match svn:ignore. :-)
On a more serious note, though, what would the proposed new definition of
svn:ignore be? Versioned-and-modified files don't get committed, but do
they get updated? Do they get omitted from 'svn log' reports? "Ignore" is
a strong verb, and if taken to the extremes implied by that verb for
versioned files, I really don't see much point in versioning them. I
*could*, however, see us growing a new property which is set on a particular
file (instead of on its parent directory) that says, "Please don't commit
me" or "Please don't commit me unless you --force it" or "Please don't
commit my text until after you commit the removal of this property" or somesuch.
C. Michael Pilato <firstname.lastname@example.org>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Thu Aug 2 14:04:46 2007