You could possibly make it so that --clean or --all is implied by --custom <br>Or that the custom option automatically detect which ones should be switched on, depending on the variables specified<br><br>just a thought<br>
regards<br>marius<br><br><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:<br><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:<br>> One more thing. When using {clean}<br>> I get bzr: ERROR: Variable {clean} is not available<br>...<br></div>Well, you may need to supply '--clean' to tell it to look for it. I<br>
haven't used the --custom format much, but when I wrote the non-custom<br>stuff, I had some enable/disable flags depending on how much time you<br>wanted it to inspect your tree. (Building up all history can take a<br>
while, as could inspecting all the files in a 50,000 file tree.)<br>--clean is probably not as expensive as it used to be, so I suppose we<br>could default that to on instead of off.<br><br>If you want to enable all values, you can do "bzr version-info --all ...".<br>
<br>John<br>=:-><br><br></blockquote></div><br>