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

Re: does "svn:ignore" not work properly in svn 1.4.3?

From: Mark Eichin <eichin_at_gmail.com>
Date: Sun, 22 Feb 2009 12:25:09 -0500

Svn:ignore won't ignore things that are already committed; you'd have to svn
rm bin as well... (if bin weren't in your repo you'd only be seeing ? Bin, I
think, not the children.) Alternatively you could ignore * on bin itself...

On Feb 22, 2009 8:58 AM, "Robert P. J. Day" <rpjday_at_crashcourse.ca> wrote:

colleague using svn 1.4.3 wanted to know how to remove all the
output from "svn status" related to generated executables that are all
placed in a working copy top-level dir named "bin".

 no problem, says i, just (from the top of the working copy):

 $ svn propset svn:ignore bin .

did that and ... no effect. i can do a "svn propget" and, sure
enough, "bin" is the sole entry for that property, but "svn status"
still insists on entering that directory and listing as unversioned,
every single generated executable in there.

 am i doing something obviously silly? thanks.

rday

--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
   Have classroom, will lecture.
http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1208905
To unsubscribe from this discussion, e-mail: [
users-unsubscribe_at_subversion.tigris.org].
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1210027
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-22 18:26:02 CET

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

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