You could possibly make it so that --clean or --all is implied by --custom  Or that the custom option automatically detect which ones should be switched on, depending on the variables specified just a thought regards marius <div class="gmail_quote">On Jan 30, 2008 9:33 PM, John Arbash Meinel <<a href="mailto:john@arbash-meinel.com">john@arbash-meinel.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">Panagiotis Papadakos wrote: > One more thing. When using {clean} > I get bzr: ERROR: Variable {clean} is not available ... </div>Well, you may need to supply '--clean' to tell it to look for it. I haven't used the --custom format much, but when I wrote the non-custom stuff, I had some enable/disable flags depending on how much time you wanted it to inspect your tree. (Building up all history can take a while, as could inspecting all the files in a 50,000 file tree.) --clean is probably not as expensive as it used to be, so I suppose we could default that to on instead of off. If you want to enable all values, you can do "bzr version-info --all ...". John =:-> </blockquote></div>