From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Marko Lindqvist <cazfi74@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] readline: apply upstream patches
Date: Thu, 29 Nov 2012 11:15:49 +0000 [thread overview]
Message-ID: <1410350.L5GQZe9fm8@helios> (raw)
In-Reply-To: <CAF6bG8erj9dh95+FKNzX_Fx7Ujm0VcMRCRO9tNFLkw6Jo033_Q@mail.gmail.com>
On Wednesday 28 November 2012 21:31:44 Marko Lindqvist wrote:
> On 28 November 2012 21:26, Saul Wold <sgw@linux.intel.com> wrote:
> > I was going to add that I think the apply=yes is default and therefore not
> > required here.
>
> Is it for files that do not have .patch suffix? With my first quick
> test it didn't work.
Correct, it is still needed in the case where there is no .patch or .diff
extension.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-11-29 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 18:27 [PATCH] readline: apply upstream patches Marko Lindqvist
2012-11-28 19:26 ` Saul Wold
2012-11-28 19:31 ` Marko Lindqvist
2012-11-29 11:15 ` Paul Eggleton [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-28 17:06 Marko Lindqvist
2012-11-28 17:45 ` Enrico Scholz
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=1410350.L5GQZe9fm8@helios \
--to=paul.eggleton@linux.intel.com \
--cc=cazfi74@gmail.com \
--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 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.