At 11/15/2005 03:52 PM, Mark Shead wrote:
> > At 11/14/2005 01:31 PM, Matt England wrote:
> > >So I find that some of my svn repos are ignoring .o files, others are
> > >not. This confounds me greatly, so I go hunting on my svn 1.2.3
>server
> > >for a global config area to control this, and I find...nothing.
>
>So when you type "svn add file.o" and then do a "svn commit file.o" it
>doesn't commit the file?
Actually, it does, apparently in both of my repos (the one that was
supposedly ignoring *.o's, and the one that was supposedly not).
I'm discovering that the apparent "difference" in the repos was poor
analysis on my part. My bad, and my apologies.
The "svn status" command is ignoring *.o files that are not under
subversion control in both (aforementioned) repos. I did a "svn add *" in
one repo--expecting that the .o file in the set would not be added--but the
.o gets added in such a case in both repos. I had assumed this was not the
case. Again, my bad.
I'm still curious as to how one manages subversion-server-wide config
properties (like global-ignore) in any case, and am a bit concerned that
there's now clear way (as of yet) that I know of for me to do this for my
svn-1.2.3 server on redhat9. Also, I'd like to know to manage
global-ignore/svn:ignore on a per-server, per-repo, and per-user basis for
one or many files or directories. The documentation seems unclear on this.
Thanks again for any help on this property-management stuff.
-Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 15 23:11:55 2005