From: Nicolas Carrier <nicolas.carrier@orolia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Added local directory as source of kernel code
Date: Fri, 9 Nov 2018 07:37:00 +0000 [thread overview]
Message-ID: <1541748990.3853.1.camel@orolia.com> (raw)
In-Reply-To: <4e18d189-1a5b-3a73-5726-4a248af87713@mind.be>
Sorry, I missed your mail, outlook is soooo awful to follow a mailing
list thread :(. I had to configure a mail client to see it.
> ?In a situation like this, you can't keep the original
> Acked/Tested/Reviewed-by
> tags, because the context has changed.
>
Ok, I wasn't sure, thank you for the explanation. If there is still a
chance that the patch can be applied, I'll repost it without the tags.
> ?Also, there is (normally) no need to keep the conflicts information
> when you
> rebase a patch.
Ok, thank you again.
And sadly, on my side, I'll have to keep this patch (and the
corresponding one for u-boot), because even if I dislike the idea of
maintaining buildroot patches locally, having kernel and u-boot
versions differ between what is built and what is set in the
configuration is, a more serious issue.
I still have some hope that this patch can be considered for inclusion
or that a clean alternative solution is proposed, though :).
Regards,
Nicolas
prev parent reply other threads:[~2018-11-09 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 10:06 [Buildroot] [PATCH 1/1] Added local directory as source of kernel code Nicolas Carrier
2018-11-07 13:57 ` Matthew Weber
2018-11-07 14:40 ` Nicolas Carrier
2018-11-07 16:44 ` Thomas Petazzoni
2018-11-07 17:08 ` Nicolas Carrier
2018-11-07 18:52 ` Yann E. MORIN
2018-11-07 21:26 ` Arnout Vandecappelle
2018-11-07 22:32 ` Yann E. MORIN
2018-11-08 10:07 ` Nicolas Carrier
2018-11-08 10:42 ` Thomas Petazzoni
2018-11-08 10:41 ` Thomas Petazzoni
2018-11-07 20:25 ` Arnout Vandecappelle
2018-11-09 7:37 ` Nicolas Carrier [this message]
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=1541748990.3853.1.camel@orolia.com \
--to=nicolas.carrier@orolia.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