From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot release and feature set
Date: Tue, 28 Aug 2018 21:57:38 -0400 [thread overview]
Message-ID: <20180829015738.GZ26633@bill-the-cat> (raw)
In-Reply-To: <VI1PR0402MB3854AB802511DE33E91E3611970A0@VI1PR0402MB3854.eurprd04.prod.outlook.com>
On Tue, Aug 28, 2018 at 06:48:13AM +0000, Prabhakar Kushwaha wrote:
> Hi Tom,
>
> Every u-boot release announcement has a very high level feature set.
> I am wondering, if you also maintain detailed feature list per u-boot release?
>
> I can see "Statistics" details per release from https://www.denx.de/wiki/U-Boot/ReleaseCycle but not the feature set.
> May be I am looking at wrong place ☹
It's been asked from time to time but I am simply bad about it. I had
tried parsing the git logs every -rc to come up with something more
detailed, but that didn't last. If more people did signed tags that
would provide some useful information for a detailed changelog.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180828/90898652/attachment.sig>
next prev parent reply other threads:[~2018-08-29 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 6:48 [U-Boot] u-boot release and feature set Prabhakar Kushwaha
2018-08-29 1:57 ` Tom Rini [this message]
2018-08-29 3:11 ` Prabhakar Kushwaha
2018-08-31 15:46 ` York Sun
2018-08-31 15:49 ` Tom Rini
2018-08-31 15:59 ` York Sun
2018-08-31 16:30 ` Tom Rini
2018-08-31 16:45 ` York Sun
2018-08-31 16:58 ` Tom Rini
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=20180829015738.GZ26633@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox