<div dir="ltr"><font color="#330033"><font size="2"><font face="tahoma,sans-serif">Thank you.<br>I'm just trying to keep track of all the changes I'm doing while working on issues.<br>It seems like you have to work your way around this, since Monticello doesn't provide you with a tool/methodology for this use case.<br>
<br><br>Avi.<br></font></font></font><br><div style="margin: 0pt;" name="sig_83fa755cf9"></div><div class="gmail_quote">On Fri, Feb 4, 2011 at 3:33 PM, Dale Henrichs <span dir="ltr"><<a href="mailto:dhenrich@vmware.com">dhenrich@vmware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Avi,<br>
<br>
I am suspicious about using a '-' to separate the author name and issueXXX .... I don't recall the exact rules that Gofer/Monticello uses in interpreting mcz file names, but I think that using the '-' where you suggest will cause issueXXX to be interpreted as the author name ... also you need to include an integer count of some sort before the .mcz extension or you will get into even more trouble.<br>
<br>
I have had success over the years using the following pattern:<br>
<br>
Seaside-Core.IssueXXX-<initials>.<count>.mcz<br>
<br>
This pattern will not be inadvertently interpreted as a Seaside-Core package by Gofer/Monticello and is very readable.<br>
<br>
Dale<br>
<div><div></div><div class="h5"><br>
On Feb 3, 2011, at 10:41 AM, Avi Shefi wrote:<br>
<br>
<br>
Hi,<br>
Assuming you are working on fixing several issues on the Seaside-Core package, what's the best way to work on issues & patches using Monticello?<br>
The best option I can think of is:<br>
1) do your work on the issue<br>
2) save it to a mcz file named: Seaside-Core-<initials>-issueXXX.mcz<br>
3) reload the original ancestor from which you started<br>
4) keep working on other issues without having the code of the previous fix inside the image<br>
<br>
This way, if you make multiple changes on the same package you will be able to send each one of them in a different file, without getting the code mixed-up along the fixes you submit.<br>
<br>
Is this the right way?<br>
<br>
<br>
Thanks,<br>
Avi.<br>
<br>
</div></div><ATT00001..txt><br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</div></div></blockquote></div><br></div>