[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [svn] Re: [Issue 2319] Showing missing properties

From: Eli Barzilay <eli_at_barzilay.org>
Date: 2005-06-02 21:43:47 CEST

On Jun 2, Thomas Moschny wrote:
> On Thursday 02 June 2005 20:20, Eli Barzilay wrote:
> > On Jun 2, kfogel@collab.net wrote:
> > > 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.
> Here's a script that might to what you want, and it's rather short
> :-) Maybe the sed part can be made more robust.
> #! /bin/bash
> comm -2 -3 \
> <( svn ls -R . | sort ) \
> <( ( svn propget -R svn:eol-style . ;
> svn propget -R svn:mime-type . ) |
> sed 's,^\(.*\) - [^ ]*$,\1,' |
> sort -u )

Well... That does work, and it's better than my version (I just added
a "| grep -v '/$'" to the `svn ls' part), but I'd say that a script
that uses two stdin redirections, and a two levels of nested subshells
is only short in its physical size... (BTW, I don't think that there
is a way to make the sed expression better -- you want the first .* to
be non-greedy, but IIRC sed is pretty limited...)

Now the real exercise would be to make that into something that can be
put on a FAQ, with instructions that are sufficient for random people
to copy, use, and modify for other situations and other properties.
This is, IMO, the impossible part.

So I still think that there is a point in adding a command line flag.
For my own usage such hacks are enough so I'll shut up now.

          ((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 21:46:24 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.