1*cd6b1674SKashyap Chamarthy.. _trivial-patches: 2*cd6b1674SKashyap Chamarthy 30c8c4514SKashyap ChamarthyTrivial Patches 40c8c4514SKashyap Chamarthy=============== 50c8c4514SKashyap Chamarthy 60c8c4514SKashyap ChamarthyOverview 70c8c4514SKashyap Chamarthy-------- 80c8c4514SKashyap Chamarthy 90c8c4514SKashyap ChamarthyTrivial patches that change just a few lines of code sometimes languish 100c8c4514SKashyap Chamarthyon the mailing list even though they require only a small amount of 110c8c4514SKashyap Chamarthyreview. This is often the case for patches that do not fall under an 120c8c4514SKashyap Chamarthyactively maintained subsystem and therefore fall through the cracks. 130c8c4514SKashyap Chamarthy 140c8c4514SKashyap ChamarthyThe trivial patches team take on the task of reviewing and building pull 150c8c4514SKashyap Chamarthyrequests for patches that: 160c8c4514SKashyap Chamarthy 170c8c4514SKashyap Chamarthy- Do not fall under an actively maintained subsystem. 180c8c4514SKashyap Chamarthy- Are single patches or short series (max 2-4 patches). 190c8c4514SKashyap Chamarthy- Only touch a few lines of code. 200c8c4514SKashyap Chamarthy 210c8c4514SKashyap Chamarthy**You should hint that your patch is a candidate by CCing 220c8c4514SKashyap Chamarthyqemu-trivial@nongnu.org.** 230c8c4514SKashyap Chamarthy 240c8c4514SKashyap ChamarthyRepositories 250c8c4514SKashyap Chamarthy------------ 260c8c4514SKashyap Chamarthy 270c8c4514SKashyap ChamarthySince the trivial patch team rotates maintainership there is only one 280c8c4514SKashyap Chamarthyactive repository at a time: 290c8c4514SKashyap Chamarthy 300c8c4514SKashyap Chamarthy- git://github.com/vivier/qemu.git trivial-patches - `browse <https://github.com/vivier/qemu/tree/trivial-patches>`__ 310c8c4514SKashyap Chamarthy 320c8c4514SKashyap ChamarthyWorkflow 330c8c4514SKashyap Chamarthy-------- 340c8c4514SKashyap Chamarthy 350c8c4514SKashyap ChamarthyThe trivial patches team rotates the duty of collecting trivial patches 360c8c4514SKashyap Chamarthyamongst its members. A team member's job is to: 370c8c4514SKashyap Chamarthy 380c8c4514SKashyap Chamarthy1. Identify trivial patches on the development mailing list. 390c8c4514SKashyap Chamarthy2. Review trivial patches, merge them into a git tree, and reply to state 400c8c4514SKashyap Chamarthy that the patch is queued. 410c8c4514SKashyap Chamarthy3. Send pull requests to the development mailing list once a week. 420c8c4514SKashyap Chamarthy 430c8c4514SKashyap ChamarthyA single team member can be on duty as long as they like. The suggested 440c8c4514SKashyap Chamarthytime is 1 week before handing off to the next member. 450c8c4514SKashyap Chamarthy 460c8c4514SKashyap ChamarthyTeam 470c8c4514SKashyap Chamarthy---- 480c8c4514SKashyap Chamarthy 490c8c4514SKashyap ChamarthyIf you would like to join the trivial patches team, contact Laurent 500c8c4514SKashyap ChamarthyVivier. The current team includes: 510c8c4514SKashyap Chamarthy 520c8c4514SKashyap Chamarthy- `Laurent Vivier <mailto:laurent@vivier.eu>`__ 53