Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TSC Meetings for the meeting of June
Date: Fri, 11 Jun 2010 20:29:15 +0200	[thread overview]
Message-ID: <hutv9r$ekh$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTikJJyDSd62eVkxlmfpjI7MgxhElzou8Kec2zcqQ@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09-06-10 15:53, Frans Meulenbroeks wrote:
> 2010/6/9 Holger Freyther <holger+oe@freyther.de>:
>> Hi all,
>>
>> we didn't really have much to talk....
>>
>>
>>
>> == Renaming the org.openmebdded.dev branch ==
>>
>> 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.

Ah well, seeing that the TSC completely failed to implement anything of
the things they decided on last month I think we can stop worrying about
this for the next few months. Does the TSC use FIFO or LIFO for their
targets?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMEoB7MkyGM64RGpERAhaEAJ4ix66HITFX983gh3axyaXRJkUEYQCgihFu
aeJb69Aqv3epd/0KxTMWgrQ=
=BqdY
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2010-06-11 18:33 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
2010-06-09 17:37       ` Khem Raj
2010-06-11  8:06         ` Frans Meulenbroeks
2010-06-11 18:29   ` Koen Kooi [this message]
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='hutv9r$ekh$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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