From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] vdr: Put common information in separate file and require it in the recipe.
Date: Sat, 09 Jan 2010 19:27:25 +0100 [thread overview]
Message-ID: <hiahqe$g5u$1@ger.gmane.org> (raw)
In-Reply-To: <1263059728.14620.64.camel@mattotaupa.wohnung.familie-menzel.net>
Paul Menzel wrote:
> Maybe there is some OE terminology to even shorten the message.
I usually call it "$PN: unify" Can't be much shorter than that ;-)
next prev parent reply other threads:[~2010-01-09 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 14:28 [PATCH] Put common information in separate file and require it in the recipe Paul Menzel
2010-01-09 15:35 ` Koen Kooi
2010-01-09 17:55 ` [PATCH] vdr: " Paul Menzel
2010-01-09 18:27 ` Rolf Leggewie [this message]
2010-01-19 9:57 ` Paul Menzel
2010-01-24 10:45 ` Holger Hans Peter Freyther
2010-01-24 13:30 ` Paul Menzel
2010-01-24 14:52 ` Holger Hans Peter Freyther
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='hiahqe$g5u$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--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.