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 12:08:28 +0100 [thread overview]
Message-ID: <hlj73b$v9k$1@ger.gmane.org> (raw)
In-Reply-To: <ac9c93b11002180211p73d24d7dv4359a61dee5a6c4e@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 18-02-10 11:11, Frans Meulenbroeks wrote:
> 2010/2/18 Koen Kooi <k.kooi@student.utwente.nl>:
> 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
>
>> The parent is http://cgit.openembedded.org/cgit.cgi/openembedded/log/packages/images/console-base-image.bb
>> we're talking about console-base-image here.
No, we are not talking about console-base-image, read the subject of
this mail: "Re: [oe] {RFC] console-image.bb"
Try doing 'git log --follow recipes/images/console-image.bb' in your OE
checkout and see the ancestry of console-image for the past 3.5 years.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLfR+sMkyGM64RGpERAohgAKCd3wFWYQNGAUKQs3DNAGZuSpSqegCffcar
DIYf1a3TDpSf/Uh5KsEhrpc=
=uB87
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-02-18 11:11 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
2010-02-18 10:11 ` Frans Meulenbroeks
2010-02-18 11:08 ` Koen Kooi [this message]
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='hlj73b$v9k$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.