From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10426] uboot-tools' fw_setenv does not update the redundant environment
Date: Fri, 20 Oct 2017 17:16:33 +0000 [thread overview]
Message-ID: <bug-10426-163-wY5JsbxM1B@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10426-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10426
Ricardo Martincoski <ricardo.martincoski@datacom.ind.br> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Ricardo Martincoski <ricardo.martincoski@datacom.ind.br> ---
(In reply to Jan Kundr?t from comment #1)
Since it is not a buildroot issue, let's close the bug as invalid.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-10-20 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 16:17 [Buildroot] [Bug 10426] New: uboot-tools' fw_setenv does not update the redundant environment bugzilla at busybox.net
2017-10-20 16:30 ` [Buildroot] [Bug 10426] " bugzilla at busybox.net
2017-10-20 16:43 ` bugzilla at busybox.net
2017-10-20 17:16 ` bugzilla at busybox.net [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=bug-10426-163-wY5JsbxM1B@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.