On 1/4/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> On 1/4/06, Mark Phippard <markp@softlanding.com> wrote:
>
> > Is there any specific reason they want this? It just doesn't sound like a
> > real requirement, it sounds more like the sort of idea you would come up
> > with as a result of trying to solve some other problem, such as showing
> > the lock info locally in decorators.
>
> It sounds to me like they're using locks as an indicator of who's
> currently working on a file, and they want to list who's holding locks
> as a way to see who's doing what. Seems like a reasonable use case to
> me.
That's exactly their use case. "Who is working on what right now?"
It doesn't seem unreasonable to me, especially when the entire project
is all binary files. It's just a communication tool.
This same team used to use a spreadsheet to accomplish the same
effect. The manager managed the spreadsheet and would email specific
files to specific team members to work on. When finished, the team
members mailed them back to the manager. The manager would then
redistribute the newest files to everyone else. In other words, the
manager was playing the role of the svn repository. People repeatedly
got used to asking the manager "who was working on what?", and only he
could answer that question. They're very excited at the idea of
subversion being able to answer that question for them.
Yeah, I guess 'svn ls -R -v dir | grep " O "' might work, but it's not
particularly friendly. What we really fits the bill is 'svnadmin
lslocks', which is the same as what RA->get_locks() returns.
Maybe it's not something that belongs in svn proper, but in some
side-tool. Dunno. Or maybe it just belongs in a GUI tool, like
scplugin.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 4 20:05:28 2006