Miscellaneous bugs

I would like to mention a few items from my private bug list. You might be able to give quick answers to some of them like "already filed" or "not a bug because ...", or an opinion on seriousness. Then I will have a better idea of which are worth filing in the issue tracker, or spending time on fixing.

None of these is very serious on its own, or I'd have mentioned it sooner.

"svn proplist": It would be useful to be able to suppress the "Properties on 'FILE':" lines, and "-q" might be an appropriate way to request that: it would match the description "print as little as possible". "svn proplist -q" currently suppresses "entry not found" warnings, but (a) those go to stderr so they are easy to suppress anyway, and (b) this could be better handled by making use of the "ignores" list.

"svn status" output is now unsorted (now that it is streamy). Needs to be sorted, for sanity.

"svn proplist ." displays the directory as "''"; should be "'.'". The same occurs in other situations too, I think. "svn propedit" was fixed in r7097.

"svn status -u gone-dir" shows children of gone-dir as normal. They should have "!" status. (gone-dir exists in repository but has been deleted from the disk.)

"svn status -v scheduled-add-dir" shows children, but "-uv" does not.

"svn cleanup" and "svn revert" ought to say whether they found anything to do, otherwise the user doesn't learn the circumstances in which it is needed, or thinks the action has been performed when in fact the wrong file was specified. In particular, it should say if it found nothing to do, as this is sort of an error: the user thought a cleanup/revert was needed, but the software disagrees.

"svn log f f2" (where f and f2 are local files) shows the log messages for f, followed by those for f2, not merged. (But "svn log file://`pwd`/repos f f2" merges the logs correctly.)

"svn log . f" in a repos-root WC shows the history of "." from 1 to its BASE followed by the history of "." (not "f") from 1 to f's BASE. "svn log a b" fails if "a" did not exist in the revision that is "b"'s working revision.

"svn log": the "Skipped <filename>" output is poor. If the file name is in svn:ignores it should silently ignore it instead, otherwise it should be an error. If this message is to be printed, it should say why the file was skipped, and it should go to stderr, in the same way the "proplist" handles such warnings.

An empty log message (-m "") is converted to a single empty line.

A repos-to-WC copy doesn't report a scheduled add ("A file"), whereas a WC-to-WC copy does.

After a straight WC-to-WC copy of a file (not a dir), "svn info" shows a wrong base "Revision:" (it should be the same as for the source, or unknown as in "svn status -v"), and "svn status -v" shows unknown last-commit revision and author. For both files and dirs, "svn status -v" shows unknown base revision.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 8 17:13:57 2003