David Waite wrote:
>I can answer this, because I've seen people as well who miss
>.cvsignore. Making .cvsignore self-referential and outside the
>repository, each user is given the ability to adjust their own local
>ignores, per-directory as they please.
>
>
What I'd like to see is a real-world example (of a project?) where it
makes sense for some project members to have their own private ignores
and where adding these to svn:ignore breaks the WC for other project
members.
And then said members of said projects should take a deep breath and
think hard for a while about things like "teamwork" and what version
control is for, _then_ discuss this issue further.
Sure, different tools produce different temporary files and I can
understand that people want those files ignored, and that you can't
force everyone on a project to use the same tools. But if ignore
patterns that would catch those files can also catch artifacts that
should be committed to the repository, then the tool that prouces them
is dangerous to use anyway.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 10 06:10:37 2004