From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11716] New: Typo on website, saying latest release is 2018.2.11
Date: Wed, 06 Mar 2019 09:35:34 +0000 [thread overview]
Message-ID: <bug-11716-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11716
Bug ID: 11716
Summary: Typo on website, saying latest release is 2018.2.11
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: trivial
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: safyannikov at perco.ru
CC: buildroot at uclibc.org
Target Milestone: ---
Typo on website, https://buildroot.org/download.html saying latest release is
2018.2.11, not 2019.2.
Filenames are correct, typo only in header
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-03-06 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 9:35 bugzilla at busybox.net [this message]
2019-03-07 9:27 ` [Buildroot] [Bug 11716] Typo on website, saying latest release is 2018.2.11 bugzilla at busybox.net
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-11716-163@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.