From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: patches can be either ".patch" or ".diff" files, yes?
Date: Fri, 18 Jul 2014 14:58:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407181455510.13980@localhost> (raw)
not sure where i saw this recently (i'll track it down), but some OE
or yocto doc claimed that patch files *must* be suffixed with
".patch". i'm pretty sure it can be either .patch or .diff, correct?
as in, it's perfectly valid to do this in a .bbappend file:
SRC_URI += "file://0001-first-change.patch"
SRC_URI += "file://0002-first-change.patch"
SRC_URI += "file://0003-first-change.diff"
as long as the filenames match, of course. yes?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2014-07-18 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 18:58 Robert P. J. Day [this message]
2014-07-18 19:30 ` patches can be either ".patch" or ".diff" files, yes? Burton, Ross
2014-07-18 21:26 ` Robert P. J. Day
2014-07-19 18:38 ` Christopher Larson
2014-07-19 18:57 ` Robert P. J. Day
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=alpine.LFD.2.11.1407181455510.13980@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@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