Aha! That was going to be my next response, saying "but when I did 'svn
add *', it still didn't ignore it!".
But that explains it.
I guess there is no way around it... What I really want is for no one to
be able to add files that end in .suo for example. I'd think that'd
have to a server-side config somewhere though. And I didn't see
anything like that except for hook scripts perhaps?
My original question is really similar to another thread that's active
right now regarding whether to do svn import or svn add/commit.
What is then, the best practice for doing an initial check-in while
ignoring some files/dirs, reasonably making things as automatic as
possible?
-----Original Message-----
From: Erik Huelsmann [mailto:ehuels@gmail.com]
Sent: Friday, September 15, 2006 3:48 PM
To: Jiho Han
Cc: Andy Levy; users@subversion.tigris.org
Subject: Re: A couple of questions on revert and svn:ignore
On 9/15/06, Jiho Han <jhan@infinityinfo.com> wrote:
> But it seems like this section from the book says otherwise:
>
> The svn:ignore property contains a list of file patterns which certain
> Subversion operations will ignore.
> Perhaps the most commonly used special property, it works in
> conjunction with the globalignores run-time configuration option (see
> the section called "Config") to filter unversioned files and
> directories out of commands svn status, svn add, and svn import.
But not when explicitly added to the list of files to commit... (which
includes 'svn add *)
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 15 21:58:38 2006