From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] knock: Fix build failure due to missing README file.
Date: Mon, 16 Dec 2013 14:39:32 +0000 [thread overview]
Message-ID: <52AF10A4.6050609@imgtec.com> (raw)
In-Reply-To: <87haadyswh.fsf@dell.be.48ers.dk>
On 12/13/2013 09:58 AM, Peter Korsgaard wrote:
>>>>>> "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.
Oh, I understand now... You changed the git version of this package to
downgrade it just to the point before the README -> README.md was made.
> If you have tested the latest git then you are welcome to send a patch
> bumping the version.
>
Yes, I have tested it, but it's easier for you to just change the
version to the last git commit number.
--
Vincent
next prev parent reply other threads:[~2013-12-16 14:39 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
2013-12-16 14:39 ` Vicente Olivert Riera [this message]
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=52AF10A4.6050609@imgtec.com \
--to=vincent.riera@imgtec.com \
--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