On Thu, Aug 10, 2017 at 2:12 AM, Christopher Li <sparse@xxxxxxxxxxx> wrote: > On Wed, Aug 9, 2017 at 3:20 PM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: >> On Wed, Aug 09, 2017 at 02:43:07AM +0200, Luc Van Oostenryck wrote: >>> Chris, >>> Please pull these patches for the upcoming release. >>> No surprise here, it's the patches that have been on >>> sparse-next, with no rebasing on external branches and >>> some extra testing. >>> >>> The following changes since commit fa71b7ac0594c9ddf81ec27753280cffef702489: >>> >>> Adding gcc attribute no_gccisr (2017-07-13 23:57:09 -0700) >>> >>> are available in the git repository at: >>> >>> git://github.com/lucvoo/sparse.git tip >>> >>> for you to fetch changes up to cccba8defbf0386305f522e63e1a1dd939f8c734: >>> >>> Bump sparse's version to -rc5 (2017-08-09 00:24:23 +0200) > > Please don't do the -rc5 bump just yet. I need to add some documents. > > I can take the master to 989132ba9259b80bc8b8bac7d9b29fabf1d9e483, the one > before -rc5 bump. Please let me do the bump. It usually come with the sign tags > as well. I have no problem for you to take only till the preceding ref. But as we agreed and so that you just have something that fast-forward to master *all* the changes must come from my tree first. I do the integration and you just pull from me. It's exactly what you asked and we agreed, right? -- Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
