[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Proposed New Features (FINAL)

From: Arild Fines <arild.fines_at_broadpark.no>
Date: 2004-03-19 23:50:03 CET

Max Bowsher wrote:
> Arild Fines wrote:
>> Max Bowsher wrote:
>>> 2) .svnignore
>>>
>>> Essentially a duplicate of the svn:ignore property.
>>
>> Is it? A .svnignore file wouldn't have to be versioned, meaning that
>> different developers can have different ignore patterns set. Very useful
if
>> the developers are using different build environments.
>
> Why not just add all the relevant ignore patterns to the repository?

But why should you be forced to version something that's essentially
private? As long as svn:ignore has to be maintained server side, it is *not*
a duplicate of the .svnignore proposal.

However, if SVN was to support the idea of a working-copy-only/nonversioned
property(a --wc-prop flag to svn ps|pe, perhaps?), it would be a different
matter. This could be useful in other situations as well - various
Subversion clients could use it for maintaining working copy-specific
metadata. I can think of at least one scenario where Ankh could find use for
this.

Was such a feature ever considered?

--
Arild
AnkhSVN: http://ankhsvn.tigris.org
Blog: http://ankhsvn.com/blog
IRC: irc://irc.freenode.net/ankhsvn
"We've got to find out what people want from fire, how they relate to it,
what sort of image it has for them.' The crowd were tense. They were
expecting something wonderful from Ford.`Stick it up your nose,' he
said.`Which is precisely the sort of thing we need to know,' insisted the
girl, `Do people want fire that can be fitted nasally?'"
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 19 23:50:12 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.