[{"data":1,"prerenderedAt":132},["ShallowReactive",2],{"term-p\u002Fpatch-series":3,"related-p\u002Fpatch-series":116},{"id":4,"title":5,"acronym":6,"body":7,"category":98,"description":99,"difficulty":100,"extension":101,"letter":16,"meta":102,"navigation":103,"path":104,"related":105,"seo":110,"sitemap":111,"stem":114,"subcategory":6,"__hash__":115},"terms\u002Fterms\u002Fp\u002Fpatch-series.md","Patch Series",null,{"type":8,"value":9,"toc":92},"minimark",[10,15,19,23,26,30,81,85,88],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 - The Vibe Check",[16,17,18],"p",{},"A patch series is the original stacked diffs, from back before pull requests existed: a numbered sequence of standalone patch files, each one a self-contained commit, submitted in order for review one at a time. Linux kernel development still runs almost entirely this way. It looks ancient next to a PR button, but it forces exactly the kind of small, reviewable, single-purpose commits that a lot of modern teams are now paying tools money to recreate.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"A patch series is an ordered set of individual patches, typically generated with git format-patch and applied with git am, representing a logical sequence of changes submitted for review as discrete, independently reviewable units, historically via a mailing list rather than a web based pull request. Projects like the Linux kernel and Git itself still use this workflow, and it directly predates and inspired the stacked diffs pattern used by web native PR tooling.",[11,27,29],{"id":28},"show-me-the-code","Show Me The Code",[31,32,37],"pre",{"className":33,"code":34,"language":35,"meta":36,"style":36},"language-bash shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","$ git format-patch main --cover-letter -o patches\u002F\n$ git am patches\u002F0001-fix-null-check.patch\n","bash","",[38,39,40,68],"code",{"__ignoreMap":36},[41,42,45,49,53,56,59,62,65],"span",{"class":43,"line":44},"line",1,[41,46,48],{"class":47},"sBMFI","$",[41,50,52],{"class":51},"sfazB"," git",[41,54,55],{"class":51}," format-patch",[41,57,58],{"class":51}," main",[41,60,61],{"class":51}," --cover-letter",[41,63,64],{"class":51}," -o",[41,66,67],{"class":51}," patches\u002F\n",[41,69,71,73,75,78],{"class":43,"line":70},2,[41,72,48],{"class":47},[41,74,52],{"class":51},[41,76,77],{"class":51}," am",[41,79,80],{"class":51}," patches\u002F0001-fix-null-check.patch\n",[11,82,84],{"id":83},"when-youll-hear-this","When You'll Hear This",[16,86,87],{},"\"The kernel still reviews everything as a patch series over the mailing list.\" \u002F \"Format-patch and git am, no pull request required.\"",[89,90,91],"style",{},"html pre.shiki code .sBMFI, html code.shiki .sBMFI{--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B}html pre.shiki code .sfazB, html code.shiki .sfazB{--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":36,"searchDepth":70,"depth":70,"links":93},[94,95,96,97],{"id":13,"depth":70,"text":14},{"id":21,"depth":70,"text":22},{"id":28,"depth":70,"text":29},{"id":83,"depth":70,"text":84},"git","A patch series is the original stacked diffs, from back before pull requests existed: a numbered sequence of standalone patch files, each one a self-contai...","intermediate","md",{},true,"\u002Fterms\u002Fp\u002Fpatch-series",[106,107,108,109],"Stacked Diffs","Rebase","Commit Hygiene","RFC",{"title":5,"description":99},{"changefreq":112,"priority":113},"weekly",0.7,"terms\u002Fp\u002Fpatch-series","65SQRLNSyBOMgY4tv3KowrCNJ5SFcMVpfNbrkS7prAI",[117,121,125,129],{"title":108,"path":118,"acronym":6,"category":98,"difficulty":119,"description":120},"\u002Fterms\u002Fc\u002Fcommit-hygiene","beginner","Commit hygiene is treating your git history like something other people, including future you, will actually have to read, not just a diary of every save p...",{"title":107,"path":122,"acronym":6,"category":98,"difficulty":123,"description":124},"\u002Fterms\u002Fr\u002Frebase","advanced","Rebase is like rewriting history.",{"title":109,"path":126,"acronym":6,"category":127,"difficulty":119,"description":128},"\u002Fterms\u002Fr\u002Frfc","general","An RFC, in modern engineering-culture speak, is a short document you write before you build something big, laying out the problem and your proposed solutio...",{"title":106,"path":130,"acronym":6,"category":98,"difficulty":100,"description":131},"\u002Fterms\u002Fs\u002Fstacked-diffs","Stacked diffs are what happens when you refuse to let one giant pull request hold a whole feature hostage.",1792528107633]