On Jun 2, kfogel@collab.net wrote:
> Eli Barzilay <eli@barzilay.org> writes:
> > That's exactly the issue... The thing that I wanted was to catch
> > all files that don't have either svn:mime-type or svn:eol-style.
> > Running:
> >
> > svn propget -R <prop> .
> >
> > will not show files that *don't* have the property, and running
> >
> > svn proplist -Rv .
> >
> > will not show files that have no properties. One solution would
> > be to use one of these, then compare that to the list of existing
> > files. Another solution would be the script I wrote. The first
> > is faster, but requires more work, and I was in my normal
> > lazy-hacker mood.
>
> Well, the full-list comparison script is the idea I was suggesting
> :-).
It will be difficult to bundle this up in a robust script. OTOH, it
would probably be trivial to change proplist.
> > My suggestion was to add a flag to proplist that will list
> > everything, just not showing the properties for paths that lack
> > them, and a similar flag to propget. propget is trickier, since
> > you don't want to see
> >
> > > propget svn:mime-type foo
> > foo -
> >
> > or
> >
> > > propget svn:mime-type foo
> > foo - no value
>
> We try not to add flags for every conceivable use case. We'd grow a
> lot of flags, most of which would not be used by most users, and
> they'd take up a lot of space in the documentation and help output.
1. This particular case (svn:eol-style and svn:mime-type) seem like
they are common problems. It seems reasonable therefore to add
some flag that will make it possible to write some short entry in
the FAQ or in the book, which tells people how to run it to detect
potential problems.
2. Since this seems to be a common problem, and if you add it to a FAQ
or to the book, then I don't think it will be a feature that gets
used by three people.
3. I consider this on the same convenience level as --stop-on-copy.
It is possible to get by without it, but soon enough you write a
script to help you. Later on when you want to make it available
for others, things get much more complicated since you actually
have to parse the output instead of relying on log messages that
don't have confusing content. Adding a flag is natural in this
case since no hacking is done, and the addition to the source is
minimal.
4. I did say that propget is trickier. For the purpose of such scan,
I'd be happy with just a proplist thing.
5. Obviously, YYMV...
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://www.barzilay.org/ Maze is Life!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 2 20:24:32 2005