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