From: "vijaikumar....@gmail.com" <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2] bitbake: Update to 1.46.2 release
Date: Mon, 5 Oct 2020 10:01:14 -0700 (PDT) [thread overview]
Message-ID: <8ab38825-8d9e-4b2a-91eb-f37084e9644en@googlegroups.com> (raw)
In-Reply-To: <CALLGG_L5k6kF_Fm+NWzSz-b_jvH1-_BirNbZ6vmPnUCHU6gdLQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1901 bytes --]
Can this be merged?
On Thursday, August 20, 2020 at 2:18:15 AM UTC+5:30
vijaikumar....@gmail.com wrote:
> Hi Henning,
>
> On Thu, Aug 20, 2020 at 1:05 AM Henning Schild
> <henning...@siemens.com> wrote:
> >
> > The mail is almost too big to handle, maybe use a cover letter for
> > potential future discussions leaving the big path in a mail nobody
> > needs to really look into.
>
> Sure. Will take care of it in future.
>
> >
> > It is always a good idea to stay up to date with upstream, but maybe
> > you have a reason on why you would like to see the bump. Last time we
> > updated bitbake we inherited some issues around git submodules. And
> > with the long due update of wic we are drifting apart and risk breaking
> > wic.
> > Any reason is fine, but if we get issues we need to know how to deal
> > with them. Maybe if a revert would be ok because the bump was more
> > cosmetic than technically needed.
>
> I started the work on wic update with a quick bitbake update.
> Later I found no technical need for the same. But the effort was already
> put and
> it made sense to complete it. Hence this upstreaming.
>
> CI-build: http://ci.isar-build.org:8080/job/isar_vkk_devel/70/
>
> WIC update is in works. And I don't(yet) see it breaking with the
> latest or the older version of
> ISAR's bitbake. Will try to send the patches soon.
>
> Thanks,
> Vijai Kumar K
>
> >
> > Henning
> >
> > Am Mon, 17 Aug 2020 21:30:09 +0530
> > schrieb Vijai Kumar K <Vijaikumar_...@mentor.com>:
> >
> > > Update bitbake to the latest 1.46.2 release.
> > > This release is tagged to the below upstream commit ID:
> > > cc11dfa4eb3616547a8a3909f89da0cc4f35dc57
> > >
> > > The version in bin/bitbake is not updated to 1.46.2 and still shows
> > > 1.46.0. Please use the above commit ID to validate it is indeed
> > > 1.46.2 release.
> > >
> > > Signed-off-by: Vijai Kumar K <Vijaikumar_...@mentor.com>
>
[-- Attachment #1.2: Type: text/html, Size: 2749 bytes --]
next prev parent reply other threads:[~2020-10-05 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 14:54 [PATCH] " Vijai Kumar K
2020-08-17 15:31 ` Jan Kiszka
2020-08-17 15:50 ` vijai kumar
2020-08-17 16:00 ` [PATCH v2] " Vijai Kumar K
2020-08-19 19:35 ` Henning Schild
2020-08-19 20:48 ` vijai kumar
2020-10-05 17:01 ` vijaikumar....@gmail.com [this message]
2020-10-23 10:31 ` Baurzhan Ismagulov
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=8ab38825-8d9e-4b2a-91eb-f37084e9644en@googlegroups.com \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox