Re: svnlook help is incomplete

On Mon, 2006-01-02 at 05:27 +0100, Vincent Lefevre wrote:
> But it doesn't say how the paths are printed. What is the exact
> format? I think that "svnlook help changed" should say more.

Tentatively agreed. I don't want to get into the trap of making "help"
a complete specification for every command, but most of our commands do
describe at least the human-readable output formats in greater detail,
and "svnlook changed" does have magic code letters in its output.

> Also, how are special characters encoded? In particular, what happens
> when some filename contains the \n character? Of course, no-one would
> normally use such a character in a filename, but I wonder about
> security holes in hook scripts using svnlook.

\n is not allowed in Subversion filenames. I believe it is an open
issue that we don't guard against them, but neither our dump format nor
our FSFS back end will handle them correctly.

Filenames are stored in UTF-8 and converted to the local character set
for output. I don't believe any other encoding of special characters is
done by svnlook changed, though I haven't consulted the code to make
sure.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 2 05:50:56 2006