Text of git-scm.com › docs › SubmittingPatches as Styx crawled it on Oct 13, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Git - SubmittingPatches Documentation

English ▾ English Topics ▾ Setup and Config git config help bugreport Credential helpers Getting and Creating Projects init clone Basic Snapshotting add status diff commit notes restore reset rm mv Branching and Merging branch checkout switch merge mergetool log stash tag worktree Sharing and Updating Projects fetch pull push remote submodule Inspection and Comparison show log diff difftool range-diff shortlog describe Patching apply cherry-pick diff rebase revert Debugging bisect blame grep Email am apply imap-send format-patch send-email request-pull External Systems svn fast-import Server Admin daemon update-server-info Guides gitattributes Command-line interface conventions Everyday Git Frequently Asked Questions (FAQ) Glossary Hooks gitignore gitmodules Revisions Submodules Tutorial Workflows All guides...

Administration clean gc fsck reflog filter-branch instaweb archive bundle Plumbing Commands cat-file check-ignore checkout-index commit-tree count-objects diff-index for-each-ref hash-object ls-files ls-tree merge-base read-tree rev-list rev-parse show-ref symbolic-ref update-index update-ref verify-pack write-tree Latest version ▾ SubmittingPatches last updated in 2.56.0 2.56.0 2026-09-28 2.55.0 2026-06-29 2.54.0 2026-04-20 2.53.0 no changes 2.52.0 2025-11-17 2.51.1 → 2.51.2 no changes 2.51.0 2025-08-18 2.48.1 → 2.50.1 no changes 2.48.0 2025-01-10 2.46.1 → 2.47.3 no changes 2.46.0 2024-07-29 2.45.4 no changes 2.45.3 2024-11-26 2.45.1 → 2.45.2 no changes 2.45.0 2024-04-29 2.43.2 → 2.44.4 no changes 2.43.1 2024-02-09 2.43.0 2023-11-20 2.42.1 → 2.42.4 no changes 2.42.0 2023-08-21 2.41.1 → 2.41.3 no changes 2.41.0 2023-06-01 2.38.3 → 2.40.4 no changes 2.38.2 2022-12-11 2.36.3 → 2.38.1 no changes 2.36.2 2022-06-23 2.36.1 no changes 2.36.0 2022-04-18 2.35.1 → 2.35.8 no changes 2.35.0 2022-01-24 2.34.2 → 2.34.8 no changes 2.34.1 2021-11-24 2.33.1 → 2.34.0 no changes 2.33.0 2021-08-16 2.32.1 → 2.32.7 no changes 2.32.0 2021-06-06 2.30.2 → 2.31.8 no changes 2.30.1 2021-02-08 2.30.0 2020-12-27 2.28.1 → 2.29.3 no changes 2.28.0 2020-07-27 2.25.1 → 2.27.1 no changes 2.25.0 2020-01-13 2.24.1 → 2.24.4 no changes 2.24.0 2019-11-04 2.22.1 → 2.23.4 no changes 2.22.0 2019-06-07 2.20.1 → 2.21.4 no changes 2.20.0 2018-12-09 2.19.1 → 2.19.6 no changes 2.19.0 2018-09-10 2.18.1 → 2.18.5 no changes 2.18.0 2018-06-21 2.17.0 → 2.17.6 no changes 2.16.6 2019-12-06 2.15.4 2019-12-06 2.14.6 no changes 2.13.7 2018-05-22 2.12.5 2017-09-22 2.10.5 → 2.11.4 no changes 2.9.5 2017-07-30 2.8.6 2017-07-30 2.4.12 → 2.7.6 no changes 2.3.10 2015-09-28 2.2.3 2015-09-04 2.1.4 no changes 2.0.5 2014-12-17 This information is specific to the Git project Please note that this information is only relevant to you if you plan on contributing to the Git project itself .

It is in no shape or form required reading for regular Git users. Guidelines Here are some guidelines for contributing back to this project. There is also a step-by-step tutorial available which covers many of these same guidelines. A typical life cycle of a patch series To help us understand the reason behind various guidelines given later in the document, first let’s understand how the life cycle of a typical patch series for this project goes.

You come up with an itch. You code it up. You do not need any pre-authorization from the project to do so. Your patches will be reviewed by other contributors on the mailing list, and the reviews will be done to assess the merit of various things, like the general idea behind your patch (including "is it solving a problem worth solving in the first place?"), the reason behind the design of the solution, and the actual implementation.

The guidelines given here are there to help your patches by making them easier to understand by the reviewers. You send the patches to the list and cc people who may need to know about the change. Your goal is not necessarily to convince others that what you are building is good. Your goal is to get help in coming up with a solution for the "itch" that is better than what you can build alone. The people who may need to know are the ones who worked on the code you are touching.

These people happen to be the ones who are most likely to be knowledgeable enough to help you, but they have no obligation to help you (i.e. you ask them for help, you don’t demand). git log -p -- $area_you_are_modifying would help you find out who they are. It is also a good idea to check whether your topic has been discussed previously on the mailing list, or whether similar work is already in progress. Prior discussions may contain useful context, design considerations, or earlier attempts at solving the same problem.

Being aware of such discussions can help you avoid duplicating work and may allow you to coordinate with other contributors working in the same area. You get comments and suggestions for improvements. You may even get them in an "on top of your change" patch form. You are expected to respond to them with "Reply-All" on the mailing list, instead of letting an updated patch series be your only response. Tell reviewers which suggestions you plan to use, which ones you disagree with, and when a comment leads you to consider a different approach.

Use these replies and any follow-up discussion as input when preparing an updated set of patches. Be particularly mindful of critiques regarding the high-level design or viability of your proposal (e.g., questioning if the feature is worth implementing, or if the chosen approach is appropriate). Defend your design decisions on the list first and work with reviewers and other members to improve the design before revising the implementation.

This will avoid wasting effort on an implementation before its design is solid. Make sure that any new version explains and justifies those design decisions more clearly, in the cover letter and in the revised commit messages. Aim to make the reviewers say "it is now clear why we may want to do this with the updated version". Topics with unresolved fundamental design critiques will not be considered ready for merging.

It is often beneficial to allow some time for reviewers to provide feedback before sending a new version, rather than sending an updated series immediately after receiving a review. This helps collect broader input, gives reviewers in different time zones a fair chance to comment, and avoids unnecessary churn from many rapid iterations. Waiting also encourages you to polish each version before sending it, so reviewers can focus on substantial issues rather than typos or other small mistakes.

As a rough default, avoid sending more than one new version of the same series per day, while considering the size of the series and the depth of review. These early update iterations are expected to be full replacements, not incremental updates on top of what you posted already. If you are correcting mistakes you made in the previous iteration that a reviewer noticed and pointed out in their review, you fix that mistake by rewriting your history (e.g., by using "git rebase -i") to pretend that you never made the mistake in the first place.

In other words, this is a chance to pretend to be a perfect developer, and you are expected to take advantage of that. In the larger picture, nobody is interested in your earlier mistakes. Just present a logical progression made by a perfect developer who makes no mistakes while working on the topic. Polish, refine, and re-send your patches to the list and to the people who spent their time to improve your patch. Go back to step (2).

While the above iterations improve your patches, the maintainer may pick the patches up from the list and queue them to the seen branch, in order to make it easier for people to play with it without having to pick up and apply the patches to their trees themselves. Being in seen has no other meaning. Specifically, it does not mean the patch was "accepted" in any way. Wh

The rest of this page is on the live site.