minor cosmetic log feature request

norris.x.pouhovitch at jpmchase.com norris.x.pouhovitch at jpmchase.com
Mon Nov 17 20:50:29 GMT 2008


Howdy all,

We use the tags facility to keep track of production deployments, and 
frequently the same exact revision of the code gets deployed to several 
distinct systems, but not always to the same system,
and we would like to keep track of which systems and components were 
affected by each deployment.
Because of that we frequently have more than a single tag for the same 
revision, let me show you an example:

$ bzr log -r282 -l 1
------------------------------------------------------------
revno: 282
tags: jss_escalation-jssdr01-p2-12550937, 
jss_escalation-jssrpt01-p2-12550937, jss_secure-jssrpt01-p2-12550937, 
jss_secure-jssdr01-p2-12550937
committer: norris.x.pouhovitch at jpmchase.com
branch nick: jss
timestamp: Sat 2008-11-15 15:20:50 -0500
message:
  Updated escalation related configuration data in the database
  and am merging these updates as well as exports of previous 
configuration
  items to the clean JSS tree.


In this case we had only four tags, in some cases the number of tags can 
baloon to as many as 12 or more
It would be great if the bzr log function would display each tag on a 
separate line, this way it would not matter how many tags any revision 
had, or how long the tag names were, they would 
still get displayed in an orderly fassion, something like this:

$ bzr log -r282 -l 1
------------------------------------------------------------
revno: 282
tag: jss_escalation-jssdr01-p2-12550937
tag: jss_escalation-jssrpt01-p2-12550937
tag: jss_secure-jssrpt01-p2-12550937
tag: jss_secure-jssdr01-p2-12550937
committer: norris.x.pouhovitch at jpmchase.com
branch nick: jss
timestamp: Sat 2008-11-15 15:20:50 -0500
message:
  Updated escalation related configuration data in the database
  and am merging these updates as well as exports of previous 
configuration
  items to the clean JSS tree.


I think the following should do it (well, it compiled and produced the 
above output):
I have not read a single python coding spec, so my stab at it may not be 
up to merging par, 
but I hope that one of the regular contributors could perhaps make it up 
to par and include it in the next
release if this feature makes sense to you guys.
$ diff log.py.1.9 log.py
784c784,785
<             to_file.write(indent + 'tags: %s\n' % (', 
'.join(revision.tags)))
---
>             for mytag in revision.tags:
>                 to_file.write(indent + 'tag: %s\n' % mytag)


btw, great tool, been using it for a long time now, and it is only getting 
better and better
great job guys

np


-----------------------------------------
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20081117/fc0d219a/attachment.htm 


More information about the bazaar mailing list