Julian Foad <julianfoad@btopenworld.com> writes:
> I have been looking for open issues that are easy to close.
Have I kissed you yet today?
> Issue 777 says "'svn log' bombs out if any arg is unversioned". The
> original problem was that it bombed out SILENTLY, but that has been
> resolved - it throws an error. The issue is still open, with the
> observation that it would be nice if it got logs for all the
> versioned arguments. While that might be nice, there is little
> point in changing it without also bringing into line the other
> subcommands which have similar behaviour.
>
> 1. I would suggest either the issue be closed as "resolved", or
> expanded in scope to "subcommands need to treat unversioned-file
> arguments in a consistent manner". Would you like me to do one of
> these?
IMHO, issue #777 should be resolved. Optionally, a new Post-1.0 issue
could be opened about log proceeding in the presence of unversioned
arguments, but as you point out, this is really a special case of a
more general question. But is that general question important enough
to be worth spending time on? I don't think so; we have many more
important bugs than this. No one's going to be prevented from getting
work done because an svn command didn't handle an unversioned target
gracefully.
Regarding open pre-1.0 issues -- if you see one that's assigned to
sussman, cmpilato, or kfogel, but it's not marked as 'STARTED', then
it's likely available if you want it. Just post first to check. Ben
can answer for me and Mike while we're on our respective vacations
:-).
Thanks for looking for issues!
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 1 06:28:56 2003