I tried this as a workaround
svn add . --force
but this exhibits the same behavior.
I haven't got a clue how svn add is implemented, but if the problem is with
globbing, shouldn't this have avoided the problem?
On 12/12/05, Gavin Lambert <gavinl@compacsort.com> wrote:
>
> Quoth Palmer Eldritch <mailto:eldritch.palmer@gmail.com>:
> > svn add ignores the value of svn:ignore which is fairly annoying
> > I'm using svn 1.2.3 on windows 2K
> >
> > steps to reproduce the incorrect behavior:
> >
> > create an empty directory 'test'
> > svn import test <repository>
> > cd test
> > svn checkout <repository> .
> > svn propset svn:ignore *.ign .
> > svn commit
> > svn propget svn:ignore .
> > ==> output:
> > *.ign
> > create files test.txt & test2.ign
> > svn status
> > ==> output:
> > ? test.txt
> > svn status --no-ignore
> > ==> output:
> > I test.ign
> > ? test.txt
> > svn add *.*
> > ==> output:
> > A test.ign
> > A test.txt
> > svn status
> > ==> output:
> > A test.ign
> > A test.txt
> > TortoiseSVN 1.2.6 build 4786 does it correctly.
>
> It's a Linux-ism, I think. Under Linux, the * on the command line is
> expanded by the shell, not the application, so svn gets the full list of
> filenames. And any filename explicitly mentioned on the commandline is
> added, regardless of ignore status (otherwise, how would you handle
> exception cases; eg. you want to keep a single .dll file in Subversion,
> even though most of the time you want to ignore them).
>
> On Windows it's the application's responsibility to expand wildcards on
> the command-line, but I imagine that all it's doing is expanding
> everything blindly and then passing it to the same code that runs on
> Linux.
>
>
Received on Tue Dec 13 10:37:48 2005