Well, I've learned something today! I wonder if I can fit my other foot in my mouth at the same time...<div><br><div class="gmail_quote">On Sat, Apr 16, 2011 at 12:33 PM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Interesting naming scheme; is that something we should "document" in<br>
MCVersionName?<br>
<br>
Also, just to clarify our words, MC _does_ support branches in the<br>
domain, just not names for them. But in terms of the ancestry, you<br>
can unlimited branching, which could be rendered if the tools were<br>
improved to do that.. Adding a name to something can often be done<br>
via external annotation, notwithstanding this naming scheme..<br>
<div><div></div><div class="h5"><br>
<br>
On Sat, Apr 16, 2011 at 11:37 AM, Colin Putney <<a href="mailto:colin@wiresong.com">colin@wiresong.com</a>> wrote:<br>
> On Fri, Apr 15, 2011 at 10:57 PM, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
><br>
>> Use some false initials that name the branch, and start its version numbers<br>
>> from e.g. 1. So I name my open-source Cog versions VMMaker-oscog.N. The<br>
>> package still has my initials as author. David is using<br>
>> VMMaker-oscog.dtl.N, etc.<br>
><br>
> Actually, MC does have some support for branching. If you use the<br>
> following convention, MC will do the "right" thing - group the<br>
> branched versions together in the UI, automatically suggest a version<br>
> name that's on a branch, and still allow you to merge between<br>
> branches. The naming convention is:<br>
><br>
> <package>.<branch>-<initials>.<id><br>
><br>
> So if Eliot were using the standard convention, his versions would be<br>
> named like this:<br>
><br>
> VMMaker.oscog-eem.147<br>
><br>
> Colin<br>
><br>
><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Casey Ransberger<br>
</div>