From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] knock: Fix build failure due to missing README file.
Date: Fri, 13 Dec 2013 10:58:06 +0100 [thread overview]
Message-ID: <87haadyswh.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <52AAD485.5040306@imgtec.com> (Vicente Olivert Riera's message of "Fri, 13 Dec 2013 09:33:57 +0000")
>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:
Hi,
>> > But of course, your patch is still relevant to send upstream!
>>
>> It afaik is already included upstream, which is why the patch no longer
>> applied.
>>
> Yes, I sent a pull request upstream and they merged it. If you have
> updated the knock.mk to use the latest git, then we don't need any
> patch because it's already applied upstream :-)
True, but the same applies with the current version we're using as that
is from before the README -> README.md rename.
If you have tested the latest git then you are welcome to send a patch
bumping the version.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-12-13 9:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 12:26 [Buildroot] [PATCH v3] knock: Fix build failure due to missing README file Vicente Olivert Riera
2013-12-12 14:27 ` Peter Korsgaard
2013-12-12 22:29 ` Arnout Vandecappelle
2013-12-12 22:50 ` Peter Korsgaard
2013-12-13 9:33 ` Vicente Olivert Riera
2013-12-13 9:58 ` Peter Korsgaard [this message]
2013-12-16 14:39 ` Vicente Olivert Riera
2013-12-16 15:14 ` Peter Korsgaard
2013-12-16 15:46 ` Vicente Olivert Riera
2013-12-16 15:50 ` Vicente Olivert Riera
2013-12-16 15:55 ` Peter Korsgaard
2013-12-16 16:38 ` Vicente Olivert Riera
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=87haadyswh.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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