svn:ignore oddness
Bruce Gray
bruce.gray at acm.org
Thu Dec 3 13:55:01 UTC 2009
On Dec 3, 2009, at 2:51 AM, Jonathan Leto wrote:
>
> I ran across this:
>
> (kadath)(~/svn/parrot)$ svn proplist t/*
--snip--
> Why are all these directories svn:ignored? I cannot generate a diff of
> my fixes to the tests in t/dynpmc with the current setup.
On my (fairly recent, r42819) local checkout:
$ svn proplist t/dynpmc
Properties on 't/dynpmc':
svn:ignore
$ svn propget svn:ignore t/dynpmc
*.pasm
*_pbcexe*
*.pbc
*.pir
md2.t
md4.t
md5.t
ripemd160.t
sha1.t
sha256.t
sha512.t
sha.t
The property "svn:ignore" does not cause the whole directory to be
ignored.
The property is used to specify a list of patterns of files to ignore.
To see the list, use `svn propget svn:ignore TARGET`
or add the `-v` option to the `svn proplist` command you used earlier.
Most of the t/ directories are set to ignore *.pasm, *.pbc, and *.pir
that
are generated (and not necessarily cleaned up) during test runs.
Might you have `global-ignores` set in your personal SVN config file?
From http://svnbook.red-bean.com/en/1.5/svn.advanced.props.special.ignore.html
:
When found on a versioned directory, the svn:ignore property is
expected
to contain a list of newline-delimited file patterns that
Subversion
should use to determine ignorable objects in that same directory.
These patterns do not override those found in the global-ignores
runtime
configuration option, but are instead appended to that list.
And it's worth noting again that, unlike the global-ignores
option, the
patterns found in the svn:ignore property apply only to the
directory
on which that property is set, and not to any of its
subdirectories.
The svn:ignore property is a good way to tell Subversion to
ignore files
that are likely to be present in every user's working copy of that
directory, such as compiler output or—to use an example more
appropriate
to this book—the HTML, PDF, or PostScript files generated as the
result
of a conversion of some source DocBook XML files to a more
legible output
format.
--
Hope this helps,
Bruce Gray (Util)
More information about the parrot-dev
mailing list