On Jul 13, 2007, at 13:57, Jean-Sebastien Pilon wrote:
>>> I came across a problem when trying to exclude files I do not which
> to
>>> monitor/version control.
>>
>> Could you give more detail on your problem and list out steps you
>> take
>> when you get the problem?
>
> I wish to exclude files which I find too noisy and that are system
> generated/modified, which do not need tracking.
>
> I did the following:
>
> $ svn pe svn:ignore /etc
>
> Added files on separate lines
>
> $ svn status
>
> That said that . (/etc) was modified...
>
> $ svn commit
>
> Now I modify the file /etc/test (which is listed in the ignores)
>
> $ svn status
>
> Says that the file is modified...
Subversion's "ignore" feature only relates to files that are not
already in the repository.
>>> How can I add files to an exclude list (even files that are already
>>> added to the repository) and avoid getting the file deleted off the
>>> system, in case I need to delete it from the repository to exclude
>>> it from further commits.
>>
>> To avoid them getting deleted? During an svn update?
>>
>> You can add ignores so that the files will not be listed in svn
>> status
>> but ignored files will be deleted in many situations.
>
> Now what I want to achieve is doable very easily when I start
> versioning
> the /etc directory on a new server. But if I want to ignore files on
> systems that are currently under version control I have no clue how to
> get it work.
Suppose you have a file foo that is in the repository and you want to
delete it from the repository but not from the working copy. You'll
need to do something like this:
cp foo foo.tmp
svn delete foo
svn ci foo -m "removing foo from repository"
mv foo.tmp foo
And you may want to set svn:ignore on the directory to ignore foo.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 14 04:40:01 2007