All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: {RFC] console-image.bb
Date: Sat, 30 Jan 2010 17:35:36 +0100	[thread overview]
Message-ID: <hk1n4n$vao$2@ger.gmane.org> (raw)
In-Reply-To: <1264865833.18482.56.camel@mattotaupa>

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

On 30-01-10 16:37, Paul Menzel wrote:
> Am Samstag, den 30.01.2010, 16:23 +0100 schrieb Koen Kooi:
>> On 30-01-10 11:35, Frans Meulenbroeks wrote:
>>> Today I bumped into console-image and noticed the following:
>>>
>>> IMAGE_INSTALL = "task-base \
>>>             ${ANGSTROM_EXTRA_INSTALL} \
>>>             ${SPLASH} \
>>>             ${ZZAPSPLASH} \
>>>
>>> Wouldn't it be cleaner to rename ANGSTROM_EXTRA_INSTALL to e.g.
>>> DISTRO_EXTRA_INSTALL ?
>>> This under the assumption that console-image is a distro independent
>> recipe.
>>>
>>> Or, in case this is an angstrom specific recipe shouldn't it be
>> better
>>> named angstrom-console-image ?
>>>
>>> your views are appreciated :-)
>>
>> I vote for leaving it as it is, it gives some credit to where it
>> originated from. The image name already has been forcefully renamed to
>> strip out 'angstrom' so lets keep at least this bit of heritage.
> 
> I think the VCS (Git) is a good tool to find out where something like
> this originated from.

It isn't when people copy stuff to overlays, or just blindly copy it
into other files.

The angstrom core developers already have a betting pool on how long it
takes for kaelios and minimal to copy newly committed changes from
angstrom to their distro configs without credit.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLZF/YMkyGM64RGpERAm3kAJ942+gMJVOCoprsQ0/4Yp2pC20TSACfQD3j
cEgUrBGvdmzm5ZoWIzZf1EU=
=kYQ/
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-01-30 16:42 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
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 [this message]
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='hk1n4n$vao$2@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.