<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi Tty,</div><div><br>On May 3, 2014, at 8:33 AM, gettimothy <<a href="mailto:gettimothy@zoho.com">gettimothy@zoho.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span></span></div></blockquote><blockquote type="cite"><div><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"><div style="font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;"><div>Hi all,<br></div><div><br></div><div>David did a mea-culpa about a monticello commit that broke some stuff and I started wondering if my commit to VMMaker-oscog broke some stuff as well as there was a gap in the commit number (I saved originally to my local cache before saving to live and forgot</div><div>that it would up the version number)</div></div></div></blockquote><div><br></div>You know that you can copy a package from your package cache? Here's the workflow...<div><br></div><div>1. Commit (which first writes the package to the package cache) but get a permissions error.</div><div><br></div><div>2. In the Monticello Browser select the <span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">package cache and click Open</span></div><div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);"><br></span></div><div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);">3. In the resulting repository inspector navigate to find and select the committed package</span></div><div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);"><br></span></div><div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);">4. Choose Copy and select the target repository from the resulting pop-up<br></span><div><br></div><div><br><blockquote type="cite"><div style="font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;"><div><span style="font-size: 10pt; ">My apologies if I broke the source tree. </span></div></div></blockquote><div><br></div>You can't :-). All you can do is commit a broken package that at worse could break some automatic tip builds. But no one has to integrate your changes if they don't want to, and you can easily commit a new fix. So don't worry unduly. It is expected that if you break it you fix it but don't feel bad about it. <br><div><br></div><br><blockquote type="cite"><div style="font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;"><div>Please call me out on my mistakes when I make them.</div><div><br></div><div>cordially,</div><div><br></div><div><br></div><div>tty.</div></div></blockquote><br><div>best,<br style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">Eliot (phone)</span></div></div></div></body></html>