From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] package/bitcoin: unset the NDEBUG flag
Date: Mon, 14 Jun 2021 18:21:21 +0200 [thread overview]
Message-ID: <20210614162121.GA2610983@scaer> (raw)
In-Reply-To: <ZTnoZb2MMbi5Z7xbG_3OKXXEj07hBkAAiKJqWo8-ke0zvQ3NE7ETdQHmw4oDe6M6YEnyDdQxIGltbNk15VM_w7hY-F7CQq8U-rG5VWRj7Uk=@senzilla.io>
Dick, All,
On 2021-06-14 10:06 +0000, D. Olsson spake thusly:
> On Sunday, June 13th, 2021 at 9:58 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> >> Signed-off-by: Dick Olsson hi at senzilla.io
> > Applied to master, thanks.
> Should we apply this to the 'next' branch as well?
> The bitcoin build is currently broken there.
Branch 'next' is closed; it has been merged back into master with commit
8d07baab43, dated 2021-06-07.
> But I'm not sure exactly how the 'master' and 'next'
> branches are managed?
https://buildroot.org/downloads/manual/manual.html#RELENG
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2021-06-14 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 20:06 [Buildroot] [PATCH 1/1] package/bitcoin: unset the NDEBUG flag Dick Olsson
2021-06-12 9:51 ` Yann E. MORIN
2021-06-13 18:04 ` [Buildroot] [PATCH v2 " Dick Olsson
2021-06-13 18:45 ` [Buildroot] [PATCH v3 " Dick Olsson
2021-06-13 19:58 ` Yann E. MORIN
2021-06-14 10:06 ` D. Olsson
2021-06-14 16:21 ` Yann E. MORIN [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=20210614162121.GA2610983@scaer \
--to=yann.morin.1998@free.fr \
--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 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.