Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TSC Meetings for the meeting of June
Date: Wed, 09 Jun 2010 12:53:10 -0400	[thread overview]
Message-ID: <4C0FC6F6.1050105@balister.org> (raw)
In-Reply-To: <AANLkTinL7xDvSoHdsxgkSumCFQNg8r3YC30gJUBcA-jO@mail.gmail.com>

On 06/09/2010 10:57 AM, Chris Larson wrote:
> On Wed, Jun 9, 2010 at 6:53 AM, Frans Meulenbroeks<
> fransmeulenbroeks@gmail.com>  wrote:
>
>> 2010/6/9 Holger Freyther<holger+oe@freyther.de<holger%2Boe@freyther.de>
>>> :
>>> We were carrying the org.openembedd.dev branch name from the monotone
>>> era into the git era and the TSC was asked to consider renaming it to
>>> 'master' which is the git default for the main development tree. Now the
>>> actual change on the server will be minor what is of a bigger concern
>>> are the existing users and documentation.
>>
>> Technically speaking I think we should have run an RFC for this before
>> it was brought to the table of the TSC.
>>
>> Personally the org.openembedded.dev branch name does not bother me
>> although I know master is the 'standard' git name.
>> Afaik renaming does not really solve a problem.
>>
>
> Personally, I have to type it at least a few times a day, it gets old, and I
> think its time we ditched monotone remnants where we're able to do so.

I'm with Chris. The name is long and annoying. It is time to drop the 
monotone/bitkeeper remnants.

Philip

>
> I am not too sure how much this affects the current users. Actually I
>> doubt if the change is bigger than the packages ->  recipes renaming
>> Isse is that if we do that we should make sure all relevant
>> documentation is updated, otherwise we only create confusion (which
>> might still creep up as people use old mailing list articles).
>>
>> Considering this, I am in favour of keeping things as they are.
>
>
> If we implement this, I don't really see a problem doing it for the users:
>
>
>>   >   c.) To ease this for existing users and to reduce the amount of
>>>       support org.openembedded.dev will track master and remains
>>>       available for a limited but long amount of time.
>>



  reply	other threads:[~2010-06-09 16:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 13:03 TSC Meetings for the meeting of June Holger Freyther
2010-06-09 13:25 ` Michael Smith
2010-06-09 13:53 ` Frans Meulenbroeks
2010-06-09 14:57   ` Chris Larson
2010-06-09 16:53     ` Philip Balister [this message]
2010-06-09 17:37       ` Khem Raj
2010-06-11  8:06         ` Frans Meulenbroeks
2010-06-11 18:29   ` Koen Kooi
2010-06-11 21:37     ` Richard Purdie
2010-06-12  7:37       ` Koen Kooi
2010-06-12 11:12       ` Frans Meulenbroeks
2010-06-12 11:47         ` Graeme Gregory
2010-06-12 12:20           ` Frans Meulenbroeks
2010-06-30 10:26 ` Holger Freyther
2010-06-30 11:05   ` Koen Kooi
2010-06-30 13:04     ` Frans Meulenbroeks
2010-06-30 13:19     ` Holger Freyther
2010-07-01  8:56       ` Koen Kooi
2010-07-01 11:52         ` Frans Meulenbroeks
2010-07-01 12:07           ` Graeme Gregory
2010-07-01 13:43             ` Frans Meulenbroeks
2010-07-01 17:59               ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C0FC6F6.1050105@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox