From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe 0/6] add syslog-ng/eventlog/libnet
Date: Wed, 20 Apr 2011 10:03:50 -0400 [thread overview]
Message-ID: <4DAEE7C6.2030101@cbnco.com> (raw)
In-Reply-To: <iom5kt$2h5$1@dough.gmane.org>
Koen Kooi wrote:
> Being able to trace the origin isn't worth having broken recipes at
> various points due to missing checksums IMO.
Yeah, in this case meta-oe is getting a newer version of a recipe than
what's in old OE, so there's not much reason to keep the history.
On the other hand if a recipe is imported into meta-oe, and it has a few
lines changed from the same version of the old OE recipe, it'd be nice
to see the changes in a commit on either old OE or meta-oe so we don't
lose the reason for the change.
Mike
prev parent reply other threads:[~2011-04-20 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 7:18 [meta-oe 0/6] add syslog-ng/eventlog/libnet Michael Lippautz
2011-04-20 7:18 ` [meta-oe 1/6] syslog-ng: Re-import 2.0.5 from org.oe.dev Michael Lippautz
2011-04-20 7:18 ` [meta-oe 2/6] eventlog: Re-import 0.2.5 " Michael Lippautz
2011-04-20 7:18 ` [meta-oe 3/6] eventlog: Clean recipe and upgrade to 0.2.12 Michael Lippautz
2011-04-20 7:24 ` Martin Jansa
2011-04-20 7:18 ` [meta-oe 4/6] libnet: Re-import 1.1.2.1 from org.oe.dev Michael Lippautz
2011-04-20 7:18 ` [meta-oe 5/6] libnet: Clean and upgrade (see below) Michael Lippautz
2011-04-20 7:30 ` Martin Jansa
2011-04-20 7:19 ` [meta-oe 6/6] syslog-ng: Update to 3.2.2 Michael Lippautz
2011-04-20 8:31 ` [meta-oe 0/6] add syslog-ng/eventlog/libnet Koen Kooi
2011-04-20 9:26 ` state of oe and meta-oe (was: 0/6] add syslog-ng/eventlog/libnet) Paul Menzel
2011-04-20 10:00 ` state of oe and meta-oe Koen Kooi
2011-04-20 10:08 ` Paul Menzel
2011-04-20 14:03 ` Michael Smith [this message]
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=4DAEE7C6.2030101@cbnco.com \
--to=msmith@cbnco.com \
--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