1Trivial Patches 2=============== 3 4Overview 5-------- 6 7Trivial patches that change just a few lines of code sometimes languish 8on the mailing list even though they require only a small amount of 9review. This is often the case for patches that do not fall under an 10actively maintained subsystem and therefore fall through the cracks. 11 12The trivial patches team take on the task of reviewing and building pull 13requests for patches that: 14 15- Do not fall under an actively maintained subsystem. 16- Are single patches or short series (max 2-4 patches). 17- Only touch a few lines of code. 18 19**You should hint that your patch is a candidate by CCing 20qemu-trivial@nongnu.org.** 21 22Repositories 23------------ 24 25Since the trivial patch team rotates maintainership there is only one 26active repository at a time: 27 28- git://github.com/vivier/qemu.git trivial-patches - `browse <https://github.com/vivier/qemu/tree/trivial-patches>`__ 29 30Workflow 31-------- 32 33The trivial patches team rotates the duty of collecting trivial patches 34amongst its members. A team member's job is to: 35 361. Identify trivial patches on the development mailing list. 372. Review trivial patches, merge them into a git tree, and reply to state 38 that the patch is queued. 393. Send pull requests to the development mailing list once a week. 40 41A single team member can be on duty as long as they like. The suggested 42time is 1 week before handing off to the next member. 43 44Team 45---- 46 47If you would like to join the trivial patches team, contact Laurent 48Vivier. The current team includes: 49 50- `Laurent Vivier <mailto:laurent@vivier.eu>`__ 51