[merge] show .bzr.log location in version output

[Robert Collins]

On Mon, 2007-07-02 at 14:59 +1000, Martin Pool wrote:
> mbp at grace% ./bzr --version
> Bazaar (bzr) 0.18.0dev0
>   from bzr checkout /home/mbp/bzr/trivial
>     revision: 2567
>     revid: mbp at sourcefrog.net-20070702044841-bhqv1470tepruga0
>     branch nick: trivial
> Using python interpreter: /usr/bin/python
> Using python standard library: /usr/lib/python2.5
> Using bzrlib: /home/mbp/bzr/trivial/bzrlib
> Using bazaar configuration: /home/mbp/.bazaar
> Logging to: /home/mbp/.bzr.log
> ^^^^^^^^^^^^^^^^^^^^^
> 
> like this.
> 
> On unix it's easy to do 'less ~/.bzr.log', but many people who need
> debugging help on windows first need to dig around to find the log
> file, and this will save some hassle.

+1

Comments:
I would say 'Bzr log file: /home...'
Rather than 'Logging to'. Or perhaps 'Using bzr log file: ...' for
consistency. Key point is to communicate that that is a file not a
program or directory or anything.

Optional:
While you are there it seems to me it would be nice to:
factor out filename selection to a function.
Give the function a test ;).

-Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070702/53d77dfa/attachment.pgp