From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <zhangyifan46@huawei.com>
Cc: <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] an idea about parallel doing do_patch
Date: Mon, 7 Sep 2020 08:58:18 +0000 [thread overview]
Message-ID: <20200907085816.GO2026@korppu> (raw)
In-Reply-To: <20610.1599468217725892636@lists.openembedded.org>
Hi, please reply to mailing list too.
On Mon, Sep 07, 2020 at 01:43:37AM -0700, zhangyifan46@huawei.com wrote:
> Sure using git repo is best solution.
> But I am working in a company and we use local codes(tar + patches).
> right or wrong, I think if we can improve the efficiency of patching, it is better than nothing.
Well, here I would really move away from tar + patches approach and move things to git.
I've been there and forced BSP vendors to provide full git trees with proper commit messages
and history linked to upstream kernel.org stable point releases. We have these
in our project and product requirements. I suggest talking to the vendors and moving
to git.
Tar and patches was ok in the 90's but not anymore large change sets.
Parallelizing do_patch() could be a nice addition but needs serious testing
and validation because bugs could have really serious effects.
Cheers,
-Mikko
next prev parent reply other threads:[~2020-09-07 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 8:27 an idea about parallel doing do_patch zhangyifan46
2020-09-07 8:37 ` [bitbake-devel] " Mikko Rapeli
[not found] ` <20610.1599468217725892636@lists.openembedded.org>
2020-09-07 8:58 ` Mikko Rapeli [this message]
2020-09-07 10:30 ` Richard Purdie
2020-09-09 23:25 ` Khem Raj
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=20200907085816.GO2026@korppu \
--to=mikko.rapeli@bmw.de \
--cc=bitbake-devel@lists.openembedded.org \
--cc=zhangyifan46@huawei.com \
/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.