From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] patch file location
Date: Tue, 22 Jun 2010 10:38:30 +0200 [thread overview]
Message-ID: <hvpsq6$2kt$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTim2-Y4qW9Wb-kycxo89vNZgBJkdeVSyERXZYCoJ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 22-06-10 09:03, Frans Meulenbroeks wrote:
> I'd like to draw the attention to the location of patch files.
> My original understanding was that these should be in either the files
> dir (if they apply to all)
No, 'files' should be avoided. When we start rearranging the directory
structure every file in 'files' will need to get checked to see to which
recipe it applies. If a patch or file is for multiple versions of recipe
foobar, place it in 'foobar/'.
Pretty much the only valid use of 'files/' is when one file is shared
between multiple different recipes (foobar_1.bb, qux_5.bb, etc), like
the gtk-doc.m4 for gnome stuff.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMIHaGMkyGM64RGpERAi+/AJ4xW0TDYMPM1zMC8tTfurDopDQpsQCaAycX
cKR3NrAdFT8lhz785DrKyeg=
=kY64
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-06-22 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 7:03 [RFC] patch file location Frans Meulenbroeks
2010-06-22 7:30 ` Marcin Juszkiewicz
2010-06-22 8:03 ` Frans Meulenbroeks
2010-06-22 8:38 ` Koen Kooi [this message]
2010-06-22 9:23 ` Phil Blundell
2010-06-22 10:25 ` Frans Meulenbroeks
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='hvpsq6$2kt$1@dough.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.