public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] Xilinx changes
Date: Wed, 18 Jan 2017 22:20:44 -0500	[thread overview]
Message-ID: <20170119032044.GF25981@bill-the-cat> (raw)
In-Reply-To: <9038a07c-378f-dbb8-5f0b-52cc6952e08e@xilinx.com>

On Thu, Jan 12, 2017 at 08:17:14AM +0100, Michal Simek wrote:
> On 12.1.2017 08:13, Masahiro Yamada wrote:
> > 2017-01-12 15:42 GMT+09:00 Michal Simek <michal.simek@xilinx.com>:
> >> On 11.1.2017 17:28, Tom Rini wrote:
> >>> On Wed, Jan 11, 2017 at 09:59:29AM +0100, Michal Simek wrote:
> >>>
> >>>> Hi Tom,
> >>>>
> >>>> here are changes I have collected. Travis is not reporting any issue.
> >>>> I have also started to use signed tags to be clear what to take.
> >>>
> >>> Ah, signed tags.  How much more work is that on your end?
> >>
> >> Almost nothing just git tag -s and write some stuff. arm-soc starts to
> >> use that long time ago that's why when you setup it once there is not an
> >> issue. Maybe good time to consider to move to the same model.
> >>
> > 
> > Interesting.
> > 
> > Maybe, will we have a key signing party in the next U-Boot mini summit?
> > The GPG certificate can be checked only when we have the chain of trust.
> 
> Tom probably has my key already from past. Definitely u-boot mini summit
> is a good opportunity for this.
> 
> > 
> > More more difference for pulling a tag commit is that
> > git always creates a merge commit
> > even if the pull-request is sitting on the top of the upstream tree.
> 
> It is up to Tom what flow he wants to use and how that merge commits
> will look like.

So, I've thought about this a bit more.  To me, at least initially, the
web of trust isn't as important as the information (and so history)
that's in the signed tags about what's coming in.  I want us to have
better release notes about what has changed and I think tags will help.
I'm not going to make it mandatory right now, I'd like people to try it
out and see what they think.  A look over
https://www.kernel.org/pub/software/scm/git/docs/howto/using-signed-tag-in-pull-request.html
may help people that haven't done it before.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170118/e925a0e3/attachment.sig>

  reply	other threads:[~2017-01-19  3:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11  8:59 [U-Boot] [GIT PULL] Xilinx changes Michal Simek
2017-01-11 16:28 ` Tom Rini
2017-01-12  6:42   ` Michal Simek
2017-01-12  7:13     ` Masahiro Yamada
2017-01-12  7:17       ` Michal Simek
2017-01-19  3:20         ` Tom Rini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-15 17:59 Michal Simek
2016-11-16  0:26 ` Masahiro Yamada
2016-11-16  7:31   ` Michal Simek
2016-11-17 22:14 ` Tom Rini
2016-09-14 11:14 Michal Simek
2016-09-18 18:04 ` Tom Rini
2016-09-19 10:00   ` Michal Simek
2016-09-19 11:13     ` Tom Rini
2016-08-02  6:25 Michal Simek
2016-08-02 17:38 ` Tom Rini
2016-07-22 13:17 Michal Simek
2016-07-23  0:10 ` Tom Rini
2016-06-06  9:26 Michal Simek
2016-06-06 21:27 ` Tom Rini
2016-05-24 11:02 Michal Simek
2016-05-24 11:16 ` Michal Simek
2016-04-13 16:37 Michal Simek
2016-04-13 19:47 ` Tom Rini
2016-04-04 18:31 Michal Simek
2016-04-05  0:01 ` Tom Rini
2016-01-27 15:42 Michal Simek
2016-01-28 23:18 ` Tom Rini
2016-02-04 13:44   ` Ricardo Ribalda Delgado

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=20170119032044.GF25981@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