Re: svn commit: rev 4187 - in trunk/subversion: clients/cmdline tests/clients/cmdline/getopt_tests_data

[Nuutti Kotivuori <na...@iki.fi>]

kfogel@tigris.org wrote:
> Implement 'svn log --quiet'.  This makes generating certain kinds of
> reports a bit more convenient.  Hint: who wants to start working on
> svnblame.py :-) ?

Hmm. Should 'svn log --quiet --xml' do what one expects?

The XML output is always parsed by a machine, so it's easy to ignore
elements that are not wanted - but on the other, it would be
consistent and perhaps useful in some edge case if '--quiet' behaved
as it does normally.

So, unless someone has more insight to the matter, I'll make sure it
respects the quiet flag sometime in the near future.

-- Naked


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn commit: rev 4187 - in trunk/subversion: clients/cmdline tests/clients/cmdline/getopt_tests_data

[Karl Fogel <kf...@newton.ch.collab.net>]

Nuutti Kotivuori <na...@iki.fi> writes:
> Hmm. Should 'svn log --quiet --xml' do what one expects?

I sort of thought -q should have no effect on svn log --xml.

> The XML output is always parsed by a machine, so it's easy to ignore
> elements that are not wanted - but on the other, it would be
> consistent and perhaps useful in some edge case if '--quiet' behaved
> as it does normally.
> 
> So, unless someone has more insight to the matter, I'll make sure it
> respects the quiet flag sometime in the near future.

It's fine if it does, too, sure.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org