Searched full:maintainers (Results 1 – 25 of 1719) sorted by relevance
12345678910>>...69
7 maintainers-include10 Implementation of the ``maintainers-include`` reST-directive.15 The ``maintainers-include`` reST-directive performs extensive parsing16 specific to the Linux kernel's standard "MAINTAINERS" file, in an32 app.add_directive("maintainers-include", MaintainersInclude)40 u"""MaintainersInclude (``maintainers-include``) directive"""44 """Parse all the MAINTAINERS lines into ReST for human-readability"""52 maintainers = False67 if descriptions and line.startswith('Maintainers'):73 # between the Maintainers heading and the first subsystem name.[all …]
9 Converter from Kconfig and MAINTAINERS to a board database.39 # Status, Arch, CPU, SoC, Vendor, Board, Target, Options, Maintainers64 *_defconfig, MAINTAINERS and Kconfig*. False otherwise.87 not filename == 'MAINTAINERS'):277 """The database of board status and maintainers."""310 """Return the maintainers of the given board.313 Maintainers of the board. If the board has two or more maintainers,317 print >> sys.stderr, "WARNING: no maintainers for '%s'" % target323 """Parse a MAINTAINERS file.325 Parse a MAINTAINERS file and accumulates board status and[all …]
24 Maintainers chapter27 The Code of Conduct uses the term "maintainers" numerous times. In the29 subsystem, driver, or file, and is listed in the MAINTAINERS file in the36 maintainers, and this needs some further clarifications.38 First and foremost, it is a reasonable expectation to have maintainers42 requirement for maintainers to unilaterally handle how other people48 Maintainers should be willing to help when problems occur, and work with50 the Technical Advisory Board (TAB) or other maintainers if you're53 uncertain about approaching the TAB or any other maintainers, please68 secondary by the expectations of contributors and maintainers.[all …]
10 contributors and maintainers pledge to making participation in our project and44 Maintainers are responsible for clarifying the standards of acceptable behavior48 Maintainers have the right and responsibility to remove, edit, or reject62 further defined and clarified by project maintainers.
131 the MAINTAINERS file for a relevant place to post. If there is a suitable136 Finding maintainers can be a bit harder. Again, the MAINTAINERS file is139 MAINTAINERS file may, in fact, not be the person who is actually acting in156 command line, it will list the maintainers who should probably receive158 get_maintainer.pl will search for maintainers; please be careful about
130 and their maintainers are:186 - Please note that most maintainers also have day jobs, so merging231 subsystem maintainers are the gatekeepers (in a loose way) for the portion235 Subsystem maintainers each manage their own version of the kernel source238 maintainers to track a list of patches, including authorship information242 When the merge window opens, top-level maintainers will ask Linus to "pull"248 trusts the subsystem maintainers to not send bad patches upstream.250 Subsystem maintainers, in turn, can pull patches from other maintainers.387 Some major subsystem maintainers use quilt to manage patches intended to go458 in the MAINTAINERS file packaged with the kernel source.
9 The upstream Linux kernel maintainers only fix bugs for specific kernel46 bug report. Some maintainers prefer bugs to be reported via bugzilla51 device driver in the MAINTAINERS file. Search in the file for relevant63 MAINTAINERS file. They can help coordinate bugfix and disclosure. See84 bugs at once, it's difficult for maintainers to tease apart the relevant145 Linux kernel maintainers expect bug reporters to be able to follow up on148 frustrating thing for maintainers is for someone to report a bug, and then155 maintainers have to assume silence means things are still broken.157 Expectations for kernel maintainers160 Linux kernel maintainers are busy, overworked human beings. Some times[all …]
78 …Summary: Test that oe-core recipes have a maintainer and entries in maintainers list have a re…79 …(except a few special static/testing ones) should have a maintainer listed in maintainers.inc file.80 Expected: All entries in maintainers list should have a recipe file that matches them99 …feature = 'require conf/distro/include/maintainers.inc\nLICENSE_FLAGS_ACCEPTED += " commercial"\nP…114 # instead of maintainers.inc129 maintainers = tinfoil.config_data.keys()130 for key in maintainers:140 … maintainer assigned to them. Please add an entry to meta/conf/distro/include/maintainers.inc file.145 The list of oe-core recipes with maintainers is empty. This may indicate that the test has regresse…150 Unable to find recipes for the following entries in maintainers.inc:
9 workflow works well for single or small numbers of maintainers but we have25 Recipe Maintainers28 See meta/conf/distro/include/maintainers.inc30 Component/Subsystem Maintainers45 Maintainers needed61 Layer Maintainers needed66 Shadow maintainers/development needed
95 Status -> "S:" entry of MAINTAINERS103 Maintainers -> "M:" entry of MAINTAINERS124 [4] Add a MAINTAINERS file125 It is generally placed at board/<board>/MAINTAINERS or126 board/<vendor>/<board>/MAINTAINERS135 [4] Update MAINTAINERS if necessary145 Board maintainers are expected to implement proper Kconfig options
37 and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify38 all of the DT maintainers.66 II. For kernel maintainers70 the devicetree maintainers for guidance. This will help them prioritize75 maintainers after a few weeks, go ahead and take it.90 devicetree maintainers overrules this document. In that situation, a patch
23 1) Maintainers, don't let perfect be the enemy of good. Don't hold up a35 the devicetree maintainers *after* discussion on the mailinglist.41 devicetree maintainers overrules this document. In that situation, a patch
7 my $input_file = "MAINTAINERS";8 my $output_file = "MAINTAINERS.new";33 --input => MAINTAINERS file to read (default: MAINTAINERS)34 --output => sorted MAINTAINERS file to write (default: MAINTAINERS.new)35 --section => new sorted MAINTAINERS file to write to (default: SECTION.new)
6 contributors and maintainers pledge to making participation in our project and36 Project maintainers are responsible for clarifying the standards of acceptable40 Project maintainers have the right and responsibility to remove, edit, or53 further defined and clarified by project maintainers.64 Project maintainers who do not follow or enforce the Code of Conduct in good
32 maintainers to Cc (from kernel MAINTAINERS_ file):55 lists and maintainers from there as well, so they are able to review66 further processing from BPF maintainers. The current queue with72 and approved by the BPF maintainers, their status in patchwork will be86 been accepted by the BPF maintainers, they will be applied to one126 maintainers know whether it is targeted at bpf or bpf-next.141 It is eventually up to the maintainers to do the delegation of280 While those patches are not processed by the BPF kernel maintainers,305 patches *prior* to submission. Never rush them! If maintainers find327 then be placed into the merge commit by the BPF maintainers such that[all …]
11 of rebasing and merging. Maintainers often get in trouble when they use19 maintainers result from a desire to avoid merges, while others come from109 Subsystem maintainers find themselves having to do two types of merges:116 Larger subsystems tend to have multiple levels of maintainers, with the117 lower-level maintainers sending pull requests to the higher levels. Acting119 is as it should be. In fact, subsystem maintainers may want to use126 Maintainers at all levels should be using signed tags on their pull127 requests, and upstream maintainers should verify the tags when pulling
6 This chapter describes how maintainers can create and submit pull requests7 to other maintainers. This is useful for transferring changes from one8 maintainers tree to another maintainers tree.47 maintainers may differ.165 maintainers may have different preferences. Also, note that if you are
10 their expectations and avoid common mistakes; maintainers may use these17 Provide an introduction to how the subsystem operates. While MAINTAINERS35 other maintainers in the submission chain.
35 Layer maintainers: Armin Kuster <akuster808@gmail.com>38 Please see the MAINTAINERS file for information on contacting the39 maintainers of this layer, as well as instructions for submitting patches.
1 This file contains a list of maintainers for the meta-networking layer.13 You may also contact the maintainers directly.26 Maintainers List (try to look for most precise areas first)
28 immediately to all translations. Translations' maintainers - and40 same change should be applied to translations. Translations' maintainers52 comfortable writing in English, you can ask the translation's maintainers
... /x11.txt u-boot-2021.07/MAINTAINERS u-boot-2021.07/Makefile u-boot ...
103 MAINTAINERS | 3 ++133 diff --git a/MAINTAINERS b/MAINTAINERS135 --- a/MAINTAINERS136 +++ b/MAINTAINERS
5 # Print selected MAINTAINERS information for226 'git-max-maintainers=i' => \$email_git_max_maintainers,307 ## Read MAINTAINERS for type/value pairs317 or die "$P: Can't open MAINTAINERS file '$file': $!\n";348 return if ($file !~ m@/MAINTAINERS$@);358 if (-d "${lk_path}MAINTAINERS") {359 opendir(DIR, "${lk_path}MAINTAINERS") or die $!;363 push(@mfiles, "${lk_path}MAINTAINERS/$file") if ($file !~ /^\./);373 push(@mfiles, "${lk_path}MAINTAINERS") if -f "${lk_path}MAINTAINERS";482 if ($file ne "MAINTAINERS" && -f $file && ($keywords || $file_emails)) {[all …]
20 * here are carefully documented so that maintainers of core and arch22 * tracing facilities. Likewise, maintainers of the tracing code do not28 * core code changing should notify the maintainers of the tracing code39 * maintainer of core code changing should notify the maintainers of the