All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Joel Stanley <joel@jms.id.au>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Eddie James <eajames@linux.ibm.com>
Subject: Re: u-boot branches
Date: Thu, 24 Sep 2020 14:02:29 -0400	[thread overview]
Message-ID: <22496.1600970549@localhost> (raw)
In-Reply-To: <CACPK8XeB3r+-6MaAO30xsj4iWpS55d7K8weUDVDAH1rw0FjOBQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 512 bytes --]


Joel Stanley <joel@jms.id.au> wrote:
    > I've chosen to rebase the openbmc changes on top of their branch. The
    > old branch is still accessible at archive/v2019.04-aspeed-openbmc-1.
    > The bitbake recipe will continue to work as it uses the nobranch=1
    > flag, and specifies the version based on the SHA.

    > The new branch contains their aspeed-master-v2019.04 tree as of today,
    > with the OpenBMC changes applied on top.

Is this any closer to upstream u-boot?
Or is it diverging further?


[-- Attachment #1.2: Signature --]
[-- Type: text/plain, Size: 241 bytes --]

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-09-24 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24  5:19 u-boot branches Joel Stanley
2020-09-24 18:02 ` Michael Richardson [this message]
     [not found] <mailman.8.1600999202.18771.openbmc@lists.ozlabs.org>
2020-10-04 19:00 ` Dan Zhang

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=22496.1600970549@localhost \
    --to=mcr@sandelman.ca \
    --cc=eajames@linux.ibm.com \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.org \
    /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.