[vim/vim] Add %check as allowed section in SPEC files. (#5531)

19 views
Skip to first unread message

Matěj Cepl

unread,
Jan 25, 2020, 1:58:49 PM1/25/20
to vim/vim, Subscribed

@ignatenkobrain What do you think?


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/5531

Commit Summary

  • Add %check as allowed section in SPEC files.

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Codecov

unread,
Jan 25, 2020, 2:19:39 PM1/25/20
to vim/vim, Subscribed

Codecov Report

Merging #5531 into master will increase coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@

##           master    #5531      +/-   ##

==========================================

+ Coverage      83%      83%   +<.01%     

==========================================

  Files         134      134              

  Lines      147991   147991              

==========================================

+ Hits       122837   122841       +4     

+ Misses      25154    25150       -4
Impacted Files Coverage Δ
src/highlight.c 82.52% <0%> (-0.27%) ⬇️
src/screen.c 84.63% <0%> (-0.23%) ⬇️
src/gui.c 63.48% <0%> (-0.16%) ⬇️
src/channel.c 84.23% <0%> (-0.08%) ⬇️
src/window.c 88.37% <0%> (-0.04%) ⬇️
src/if_xcmdsrv.c 86.17% <0%> (ø) ⬆️
src/drawline.c 84.8% <0%> (+0.13%) ⬆️
src/os_unix.c 63.63% <0%> (+0.22%) ⬆️
src/ui.c 72.32% <0%> (+1.11%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1d9215b...e76022f. Read the comment docs.

Igor Gnatenko

unread,
Feb 6, 2020, 4:01:25 PM2/6/20
to vim/vim, Subscribed

LGTM

Matěj Cepl

unread,
Feb 6, 2020, 5:19:02 PM2/6/20
to vim/vim, Subscribed

LGTM

So, how I should proceed to get this merged?

Christian Brabandt

unread,
Feb 7, 2020, 2:44:17 AM2/7/20
to vim/vim, Subscribed

the usual way is to have the runtime file maintainer send an update to Bram for inclusion.

Matěj Cepl

unread,
Feb 7, 2020, 8:21:30 AM2/7/20
to vim/vim, Subscribed

the usual way is to have the runtime file maintainer send an update to Bram for inclusion.

The hope that Bram would actually follow vim_dev is probably just a fantasy, right?

Igor Gnatenko

unread,
Feb 7, 2020, 8:28:44 AM2/7/20
to vim/vim, Subscribed

I remember in past @brammool has merged runtime PR related to spec.vim where I gave lgtm. Let's see if this is still the case...

Bram Moolenaar

unread,
Feb 7, 2020, 2:20:02 PM2/7/20
to vim/vim, Subscribed

I'll include it and update the date in the header, thanks.

Bram Moolenaar

unread,
Feb 7, 2020, 2:20:09 PM2/7/20
to vim/vim, Subscribed

Closed #5531.

Bram Moolenaar

unread,
Feb 7, 2020, 2:51:05 PM2/7/20
to vim...@googlegroups.com, Matěj Cepl

> > the usual way is to have the runtime file maintainer send an update
> > to Bram for inclusion.
>
> The hope that Bram would actually follow ``vim_dev`` is probably just
> a fantasy, right?

Fantasies may come true! :-)

--
Those who live by the sword get shot by those who don't.

/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
Reply all
Reply to author
Forward
0 new messages