From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
Martin Jansa <martin.jansa@gmail.com>,
akuster <akuster@mvista.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH]] bitbake: update masters version to some farout version
Date: Mon, 15 Apr 2019 14:34:06 +0100 [thread overview]
Message-ID: <0d355dec3e98f63d574ad1967608556becc4a5fe.camel@linuxfoundation.org> (raw)
In-Reply-To: <1c452d27-33c3-234b-9d57-b39689d3c3f9@gmail.com>
On Fri, 2019-04-12 at 08:39 -0700, akuster808 wrote:
>
>
> On 4/12/19 1:06 PM, Martin Jansa wrote:
> > > but so how is it Master is 1.40
> >
> > It isn't, master is currently identical with 1.42 branch, so both
> > are 1.42.
> Yes you are correct. As of this email it is.
>
> Three hours ago master was updated to 1.42
> https://git.openembedded.org/bitbake/commit/?id=00b133af009f9e7c1a4c751b6ef4902f47a81fe2
>
> Master then got bumped to 1.43
> https://git.openembedded.org/bitbake/commit/?id=aae15f3c16fb463962eee100a8b0bcd5fc01ad96
>
> again three hours ago.
>
> so now all it right with the world. : )
Just to follow up this was basically the release process working.
Master was in sync with 1.42, we released and 1.42 ended in the branch,
1.43 continued in master...
Cheers,
Richard
prev parent reply other threads:[~2019-04-15 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 1:19 [PATCH]] bitbake: update masters version to some farout version Armin Kuster
2019-04-12 2:53 ` Christopher Larson
2019-04-12 6:04 ` akuster
2019-04-12 7:36 ` Martin Jansa
2019-04-12 15:39 ` akuster808
2019-04-15 13:34 ` Richard Purdie [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=0d355dec3e98f63d574ad1967608556becc4a5fe.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=martin.jansa@gmail.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.