From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot release and feature set
Date: Fri, 31 Aug 2018 12:30:37 -0400 [thread overview]
Message-ID: <20180831163037.GU26633@bill-the-cat> (raw)
In-Reply-To: <DB7PR04MB42983267E2E5E2F4F35082FF9A0F0@DB7PR04MB4298.eurprd04.prod.outlook.com>
On Fri, Aug 31, 2018 at 03:59:59PM +0000, York Sun wrote:
> On 08/31/2018 08:49 AM, Tom Rini wrote:
> > I really would appreciate the level of detail Linus' tree gets in signed
> > commit messages being in the U-Boot tree too. No, it's not perfect and
> > it does need someone to make it more digestible, but it's a good
> > starting point. And the people that do send me signed tags do a good
> > job too I think.
> >
>
> If you prefer to have signed tags, we can start to do this. Would you
> write some guideline on the format, and what information should be
> included in the annotated tags, how often do we tag?I guess you will use
> a script to extract information, unless you want to read all of them.
I will admit that I had to manually find this email link as perhaps my
subject at the time was not the best:
https://lists.denx.de/pipermail/u-boot/2018-June/330610.html
If information is in the merge commit then it's a lot easier to do
anything more on top of that. Thanks!
--
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/20180831/9e575725/attachment.sig>
next prev parent reply other threads:[~2018-08-31 16:30 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
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 [this message]
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=20180831163037.GU26633@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