<div dir="auto">I am hoping April 1st has something to do with this. I can't imagine the confusion that could arise from these three names.<div dir="auto"><br></div><div dir="auto">Scott </div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Apr 1, 2018, 10:57 AM akuster808 <<a href="mailto:akuster808@gmail.com">akuster808@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 04/01/2018 02:22 AM, Burton, Ross wrote:<br>
> On 1 April 2018 at 06:21, Richard Purdie<br>
> <<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank" rel="noreferrer">richard.purdie@linuxfoundation.org</a>> wrote:<br>
>> Following on from sumo and very in keeping with naming schemes, I'm<br>
>> therefore proposing we should have the "there" release. This would be<br>
>> followed by the "their" release and then the "theyre" release, making<br>
>> us really out 'there'! The latter is a bit of a compromise as I'm not<br>
>> sure an apostrophe would be easily handled in the branch names.<br>
> I know I'm sounding a bit like a scratched record, but can we try and<br>
> keep the names alphabetical?<br>
><br>
> sumo -> their -> there -> theyre<br>
<br>
The concern is maintenance. Having branches that close in name, may<br>
cause confusion when backport patches. Please back port to "Their" , no<br>
sorry, I meant There. Not Theyre..<br>
<br>
And if we verbally refer to any one of those branches, How will you know<br>
which on without spelling it our or defaulting to There #1, There #2, etc.<br>
<br>
- Armin<br>
<br>
><br>
> Other than that, +1 from me.<br>
><br>
> Ross<br>
> _______________________________________________<br>
> Openembedded-architecture mailing list<br>
> <a href="mailto:Openembedded-architecture@lists.openembedded.org" target="_blank" rel="noreferrer">Openembedded-architecture@lists.openembedded.org</a><br>
> <a href="http://lists.openembedded.org/mailman/listinfo/openembedded-architecture" rel="noreferrer noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-architecture</a><br>
<br>
<br>
_______________________________________________<br>
Openembedded-architecture mailing list<br>
<a href="mailto:Openembedded-architecture@lists.openembedded.org" target="_blank" rel="noreferrer">Openembedded-architecture@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-architecture" rel="noreferrer noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-architecture</a><br>
</blockquote></div>