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

Re: [TSVN] More ignore trouble

From: Simon Large <simon_at_skirridsystems.co.uk>
Date: 2005-07-10 00:10:28 CEST

Thomas Beale wrote:
> The files I want to ignore in a particular repository have names like
> openEHR-EHR-EVALUATION.problem-diagnosis-histological.v1.adl2
>
> I am using the ignore pattern *.adl2

If the file is not already in the repository, that pattern should ignore
it. Try the command line client too. But note that the ignore pattern is
case-sensitive, so if the actual extension is .ADL2, then your pattern
will not work.

> Here is what I have tried:
> - setting *.adl2 in the ignore/exclude list on the settings dialog (what
> does TSVN do with this value?)

Well TSVN does nothing. You are adding it to the subversion config file
and it is subversion which uses it. This should work provided the case
is correct. There is a hierarchy of places which SVN looks for config
information, so there is a small possibility that it is being overridden
from somewhere else. See this FAQ article:

http://tortoisesvn.sourceforge.net/?q=node/29

> - setting svn:ignore = *.adl2 in the top directory of the repository

No, that won't work. SVN doesn't search up the hierarchy.

> - choosing a file and telling TSVN to ignore files of that pattern (I
> assume this sets svn:ignore on the immediate owning directory -
> consistent with what I see in properties).

Yes, that is correct.

> I think only the last one is working. But this means I have to repeat
> that action on every directory in the repository. Ok, it's easy for me -
> I have cygwin and can do a find . -name *.adl2 -exec propset ....., but
> this is going to be difficult to explain to many of our users who are
> just windows/gui people. If they create a new directory sometime down
> the track, will that directory inherit the property settings of the
> parent? I think it should. Otherwise people are going to go a bit crazy
> not understanding why things that seemed to work before (in some
> directory) now don't work in the new directory.
>
> I have read most of the doc, and FAQs, and I have the impression that
> there is no place for settings for a reposiotry as a whole; it is either
> 'the client machine (all repositories)' or 'per-directory'. Am I missing
> something here?

You are right, that is exactly what happens. One of the discussion
subjects within subversion at the moment is inherited properties, which
are not yet implemented. Whether this particular one will be made
inheritable I do not know.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Jul 10 00:09:43 2005

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