Mailing Patches
Once you have generated a patch or a series of patches, the next logical step is to send them to another developer or to a development list for review, with an ultimate goal of having them picked up by a developer or upstream maintainer and applied to another repository.
The formatted patches are generally intended to be sent via email by directly importing them into your mail user agent (MUA) or by using Git’s git send-email command. You are not obliged to use git send-email; it is merely a convenience. As you will see in the next section, there are also other tools that use the patch file directly.
Assuming that you want to send a generated patch file to another developer, there are several ways to send the file: you can run git send-email; you can point your mailer directly to the patches; or you can include the patches in a piece of email.
Using git send-email is straightforward. In
this example, the patch 0001-A.patch is sent to a
mail list called devlist@example.org:
$ git send-email -to devlist@example.org 0001-A.patch 0001-A.patch Who should the emails appear to be from? [Jon Loeliger <jdl@example.com>] Emails will be sent from: Jon Loeliger <jdl@example.com> Message-ID to be used as In-Reply-To for the first email? (mbox) Adding cc: Jon Loeliger <jdl@example.com> from line 'From: Jon Loeliger <jdl@example.com>' OK. Log says: Sendmail: /usr/sbin/sendmail -i devlist@example.org jdl@example.com From: Jon Loeliger <jdl@example.com> To: devlist@example.org Cc: Jon ...Get Version Control with Git now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
