I use the following line to find all sub-directories of the PWD and run svnadmin verify on each directory (I already know that they're Subversion repositories)

find ./* -maxdepth 0 -exec svnadmin verify {} \;


This works well, other than the fact that the output looks like this:

* Verifying repository metadata ...
* Verifying metadata at revision 1 ...
* Verifying metadata at revision 2 ...
* Verifying metadata at revision 4 ...
* Verifying metadata at revision 5 ...
* Verifying metadata at revision 6 ...
* Verifying metadata at revision 9 ...
* Verifying metadata at revision 10 ...
* Verifying metadata at revision 12 ...
* Verifying metadata at revision 14 ...
* Verifying metadata at revision 15 ...
* Verifying metadata at revision 18 ...
* Verifying metadata at revision 20 ...
* Verifying metadata at revision 22 ...
* Verified revision 0.
* Verified revision 1.
* Verified revision 2.
* Verified revision 3.
* Verified revision 4.
* Verified revision 5.
* Verified revision 6.
* Verified revision 7.
* Verified revision 8.
* Verified revision 9.
* Verified revision 10.
* Verified revision 11.
* Verified revision 12.
* Verified revision 13.
* Verified revision 14.
* Verified revision 15.
* Verified revision 16.
* Verified revision 17.
* Verified revision 18.
* Verified revision 19.
* Verified revision 20.
* Verified revision 21.
* Verified revision 22.
* Verified revision 23.
* Verified revision 0.
* Verifying repository metadata ...
* Verifying metadata at revision 4 ...
* Verifying metadata at revision 5 ...
* Verifying metadata at revision 6 ...
* Verifying metadata at revision 7 ...
* Verifying metadata at revision 9 ...
* Verified revision 0.
* Verified revision 1.
* Verified revision 2.
* Verified revision 3.
* Verified revision 4.
* Verified revision 5.
* Verified revision 6.
* Verified revision 7.
* Verified revision 8.
* Verified revision 9.


I'd really like find to print the filename before executing the svnadmin verify command, to make logging easier.

I've tried to squeeze a little ls in there but bodged it up, how should I do this (preferably simply)?


Question: In-game rewards for game-related work?
Answer: I was first introduced to this idea in the Amber Diceless Roleplaying Game, which encouraged player involvement by awarding Good Stuff (a mix of character-building points and general karma) for out-of-character actions.

The main ones used there were more fitting for the Amber setting - drawing character cards (Trumps) of the characters, or writing in-character diaries for the character, which worked fantastically for our game, since in addition to having us think of the characters between session, created a running documentary of the campaign. Additionally, this scales up to however many players want in, though it's not necessarily as useful for a dungeon-crawling sort of game.

Other options for us involved the rather prosaic driving duties - a player who regularly picked up transportationally-challenged players and drove them to and from the sessions was rewarded, as were the players who build the campaign website (now sadly offline, I really need to put it back up).

I don't have the Amber Diceless book any more, but if you can get your hands on it (there's a PDF version being sold at DrivethruRPG) you can look up their suggestions for player rewards.