From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] renaming packages/ to recipes/
Date: Fri, 27 Feb 2009 01:44:14 +0900 [thread overview]
Message-ID: <go6gt0$5hp$1@ger.gmane.org> (raw)
In-Reply-To: <49A69217.3070705@opensimpad.org>
Bernhard Guillon wrote:
>> mkdir recipes-broken
>> git add recipes-broken
>> git mv recipes/obsolete recipes-broken/obsolete
>> git mv recipes/nonworking recipes-broken/nonworking
+1
> I like this idea. But we should add a description file to the recipe on
> which arch it is broken or why it is obsolete.
Oh no, please no. Not yet another file which people will ignore ;-)
That is what the commit message and "git log
recipes/obsolete/$somepackage" is for.
next prev parent reply other threads:[~2009-02-26 16:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 20:21 [RFC] renaming packages/ to recipes/ Koen Kooi
2009-02-25 20:27 ` Henning Heinold
2009-02-25 20:37 ` Koen Kooi
2009-02-25 20:48 ` Mike (mwester)
2009-02-25 21:00 ` Merge windows, was: " Koen Kooi
2009-02-25 21:15 ` Michael 'Mickey' Lauer
2009-02-25 21:22 ` Koen Kooi
2009-02-26 0:56 ` Otavio Salvador
2009-02-26 9:09 ` Yuri Bushmelev
2009-02-25 20:41 ` Denys Dmytriyenko
2009-02-25 20:54 ` Koen Kooi
2009-02-26 6:52 ` Sledz, Steffen
2009-02-26 8:24 ` Martyn Welch
2009-02-26 10:44 ` Marcin Juszkiewicz
2009-02-26 12:59 ` Bernhard Guillon
2009-02-26 15:38 ` Yuri Bushmelev
2009-02-26 16:44 ` Rolf Leggewie [this message]
2009-03-04 11:27 ` Andrea Adami
2009-05-17 23:35 ` Rolf Leggewie
2009-05-17 23:56 ` Tom Rini
2009-05-19 12:19 ` Frans Meulenbroeks
2009-05-19 13:02 ` Philip Balister
2009-05-19 13:33 ` Koen Kooi
2009-05-19 14:02 ` Elena of Valhalla
2009-05-19 14:32 ` Frans Meulenbroeks
2009-02-26 11:08 ` Robert Schuster
2009-02-26 13:43 ` Leon Woestenberg
2009-03-04 11:16 ` Koen Kooi
2009-03-04 15:30 ` Tom Rini
2009-03-04 16:38 ` Koen Kooi
2009-03-05 15:35 ` Otavio Salvador
2009-03-13 18:10 ` Rob Tow
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='go6gt0$5hp$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.