From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: {RFC] console-image.bb
Date: Thu, 18 Feb 2010 10:42:06 +0100 [thread overview]
Message-ID: <hlj21d$fdf$1@ger.gmane.org> (raw)
In-Reply-To: <ac9c93b11002180118m1512bc71sa6eb91624e83263e@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 18-02-10 10:18, Frans Meulenbroeks wrote:
> 2010/2/17 Koen Kooi <k.kooi@student.utwente.nl>:
>
>>>> FYI: I popped a question three weeks ago.
>>>> Today Rolf asked me about the status in #oe.
>>>> As you can see above 4 people (Rolf, Mickey, Phil and me were in
>>>> favour of the proposal. In irc mckoan also backed the proposal.
>>>> There was one person opposed to it: you.
>>
>> And funnily enough I'm the maintainer, so I get the final say.
>
> Still wondering what makes you the maintainer.
>
> git log does not mention any changes for this file by you (apart from
> yesterdays revert):
> See http://cgit.openembedded.org/cgit.cgi/openembedded/log/recipes/images/console-base-image.bb
Git doesn't track renames properly, using the parent of the
packages->recipes commit:
http://cgit.openembedded.org/cgit.cgi/openembedded/log/packages/images/console-image.bb?id=fa6cd5a3b993f16c27de4ff82b42684516d433ba
And that stops on a rename as well.
>
> Btw in the commit message you write
> "If you're touching a recipe at least make sure the creator/maintainer
> agrees with your changes."
>
> How come this "rule" suddenly appears.
It hasn't suddenly appeared, and furthermore console-image is widely
used enough to label it 'core', so any changes will need to get
reviewed, which they weren't in this case.
And non-angstrom people created angstrom-named new recipes without any
approval from angstrom developers is just plain rude.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLfQtuMkyGM64RGpERAuLxAJ9nhJE4wv6U+TDleoStwvk+suGAhACguLZF
2RCLURHCtcP3Zq21cd3VjNo=
=tR5o
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-02-18 9:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 10:35 {RFC] console-image.bb Frans Meulenbroeks
2010-01-30 10:47 ` Rolf Leggewie
2010-01-30 10:53 ` Frans Meulenbroeks
2010-01-30 12:24 ` Michael 'Mickey' Lauer
2010-01-30 14:26 ` Philip Balister
2010-02-17 18:20 ` Koen Kooi
2010-02-17 18:33 ` Rolf Leggewie
2010-02-17 19:29 ` Philip Balister
2010-02-18 12:35 ` Rolf Leggewie
2010-02-17 18:58 ` Frans Meulenbroeks
2010-02-17 19:12 ` Koen Kooi
2010-02-17 19:40 ` Frans Meulenbroeks
2010-02-17 19:47 ` Koen Kooi
2010-02-17 19:52 ` Frans Meulenbroeks
2010-02-18 9:18 ` Frans Meulenbroeks
2010-02-18 9:42 ` Koen Kooi [this message]
2010-02-18 10:11 ` Frans Meulenbroeks
2010-02-18 11:08 ` Koen Kooi
2010-02-18 11:34 ` Frans Meulenbroeks
2010-02-18 12:38 ` Rolf Leggewie
2010-02-18 13:47 ` Richard Purdie
2010-01-30 15:23 ` Koen Kooi
2010-01-30 15:37 ` Paul Menzel
2010-01-30 16:35 ` Koen Kooi
2010-01-30 16:54 ` Michael 'Mickey' Lauer
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='hlj21d$fdf$1@ger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.