| blob | 0fc53b9f1c49591d572eb362d52192b53c196f74 |
4 <head>
9 /* Debug borders */
11 /*
12 border: 1px solid red;
13 */
14 }
16 body {
18 }
20 a {
23 }
26 }
28 em {
31 }
33 strong {
36 }
38 tt {
40 }
48 }
52 }
53 h2 {
55 }
56 h3 {
58 }
59 h3 + * {
61 }
66 }
68 hr {
70 }
72 p {
75 }
79 }
81 pre {
84 }
86 span#author {
91 }
92 span#email {
93 }
96 }
98 div#footer {
104 }
105 div#footer-text {
108 }
109 div#footer-badges {
112 }
114 div#preamble {
117 }
123 }
127 }
131 }
133 /* Block element titles. */
141 }
144 }
148 }
151 }
154 }
160 }
166 }
171 }
175 }
180 }
183 }
187 }
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 }
200 }
204 }
209 }
215 dl {
218 }
219 dt {
224 }
227 }
231 }
234 }
237 }
240 }
243 }
246 }
253 }
257 }
258 thead {
261 }
262 tfoot {
264 }
267 }
270 }
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 }
278 }
282 }
288 }
291 }
294 }
300 }
303 }
307 }
311 }
315 }
317 div#toctitle {
324 }
329 }
333 }
337 }
341 }
342 /* Overrides for manpage documents */
343 h1 {
348 }
349 h2 {
351 }
354 }
358 }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
366 }
373 }
379 }
384 }
388 }
392 }
397 }
399 /* IE6 sets dynamically generated links as visited. */
401 </style>
402 </head>
403 <body>
405 <h1>
406 git-format-patch(1) Manual Page
407 </h1>
410 <p>git-format-patch -
411 Prepare patches for e-mail submission
412 </p>
413 </div>
414 </div>
418 <div class="verseblock-content"><em>git format-patch</em> [-k] [(-o|--output-directory) <dir> | --stdout]
421 [-s | --signoff]
423 [-n | --numbered | -N | --no-numbered]
426 [--ignore-if-in-upstream]
427 [--subject-prefix=Subject-Prefix]
429 [--cover-letter] [--quiet]
433 </div></div>
434 </div>
438 one file per commit, formatted to resemble UNIX mailbox format.
439 The output of this command is convenient for e-mail submission or
443 <li>
444 <p>
446 to the tip of the current branch that are not in the history
448 </p>
449 </li>
450 <li>
451 <p>
454 commits in the specified range.
455 </p>
456 </li>
457 </ol></div>
458 <div class="paragraph"><p>The first rule takes precedence in the case of a single <commit>. To
459 apply the second rule, i.e., format everything since the beginning of
463 <div class="paragraph"><p>By default, each output file is numbered sequentially from 1, and uses the
464 first line of the commit message (massaged for pathname safety) as
466 will only be numbers, without the first line of the commit appended.
467 The names of the output files are printed to standard
469 <div class="paragraph"><p>If <tt>-o</tt> is specified, output files are created in <dir>. Otherwise
470 they are created in the current working directory.</p></div>
472 the subject when multiple patches are output is "[PATCH n/m] First
475 <div class="paragraph"><p>If given <tt>--thread</tt>, <tt>git-format-patch</tt> will generate <tt>In-Reply-To</tt> and
478 reference.</p></div>
479 </div>
484 -p
485 </dt>
487 --no-stat
488 </dt>
489 <dd>
490 <p>
491 Generate plain patches without any diffstats.
492 </p>
493 </dd>
496 </dt>
499 </dt>
500 <dd>
501 <p>
503 the usual three.
504 </p>
505 </dd>
507 --patience
508 </dt>
509 <dd>
510 <p>
511 Generate a diff using the "patience diff" algorithm.
512 </p>
513 </dd>
516 </dt>
517 <dd>
518 <p>
519 Generate a diffstat. You can override the default
521 The width of the filename part can be controlled by
522 giving another width to it separated by a comma.
523 </p>
524 </dd>
526 --numstat
527 </dt>
528 <dd>
529 <p>
531 deleted lines in decimal notation and pathname without
532 abbreviation, to make it more machine friendly. For
535 </p>
536 </dd>
538 --shortstat
539 </dt>
540 <dd>
541 <p>
543 number of modified files, as well as number of added and deleted
544 lines.
545 </p>
546 </dd>
549 </dt>
550 <dd>
551 <p>
552 Output the distribution of relative amount of changes for each
554 passing it a comma separated list of parameters.
557 The following parameters are available:
558 </p>
562 </dt>
563 <dd>
564 <p>
565 Compute the dirstat numbers by counting the lines that have been
566 removed from the source, or added to the destination. This ignores
567 the amount of pure code movements within a file. In other words,
568 rearranging lines in a file is not counted as much as other changes.
569 This is the default behavior when no parameter is given.
570 </p>
571 </dd>
574 </dt>
575 <dd>
576 <p>
577 Compute the dirstat numbers by doing the regular line-based diff
578 analysis, and summing the removed/added line counts. (For binary
579 files, count 64-byte chunks instead, since binary files have no
582 lines within a file as much as other changes. The resulting output
584 </p>
585 </dd>
588 </dt>
589 <dd>
590 <p>
591 Compute the dirstat numbers by counting the number of files changed.
592 Each changed file counts equally in the dirstat analysis. This is
594 not have to look at the file contents at all.
595 </p>
596 </dd>
599 </dt>
600 <dd>
601 <p>
602 Count changes in a child directory for the parent directory as well.
604 reported may exceed 100%. The default (non-cumulative) behavior can
606 </p>
607 </dd>
610 </dt>
611 <dd>
612 <p>
613 An integer parameter specifies a cut-off percent (3% by default).
614 Directories contributing less than this percentage of the changes
615 are not shown in the output.
616 </p>
617 </dd>
618 </dl></div>
620 directories with less than 10% of the total amount of changed files,
621 and accumulating child directory counts in the parent directories:
623 </dd>
625 --summary
626 </dt>
627 <dd>
628 <p>
629 Output a condensed summary of extended header information
630 such as creations, renames and mode changes.
631 </p>
632 </dd>
634 --no-renames
635 </dt>
636 <dd>
637 <p>
638 Turn off rename detection, even when the configuration
639 file gives the default to do so.
640 </p>
641 </dd>
643 --full-index
644 </dt>
645 <dd>
646 <p>
647 Instead of the first handful of characters, show the full
648 pre- and post-image blob object names on the "index"
649 line when generating patch format output.
650 </p>
651 </dd>
653 --binary
654 </dt>
655 <dd>
656 <p>
659 </p>
660 </dd>
663 </dt>
664 <dd>
665 <p>
666 Instead of showing the full 40-byte hexadecimal object
667 name in diff-raw format output and diff-tree header
668 lines, show only a partial prefix. This is
670 the diff-patch output format. Non default number of
672 </p>
673 </dd>
676 </dt>
679 </dt>
680 <dd>
681 <p>
682 Break complete rewrite changes into pairs of delete and
683 create. This serves two purposes:
684 </p>
686 not as a series of deletion and insertion mixed together with a very
687 few lines that happen to match textually as the context, but as a
688 single deletion of everything old followed by a single insertion of
691 original should remain in the result for git to consider it a total
692 rewrite (i.e. otherwise the resulting patch will be a series of
693 deletion and insertion mixed together with context lines).</p></div>
695 source of a rename (usually -M only considers a file that disappeared
699 eligible for being picked up as a possible source of a rename to
700 another file.</p></div>
701 </dd>
704 </dt>
707 </dt>
708 <dd>
709 <p>
710 Detect renames.
712 index (i.e. amount of addition/deletions compared to the
714 delete/add pair to be a rename if more than 90% of the file
715 hasn’t changed.
716 </p>
717 </dd>
720 </dt>
723 </dt>
724 <dd>
725 <p>
728 </p>
729 </dd>
731 --find-copies-harder
732 </dt>
733 <dd>
734 <p>
736 if the original file of the copy was modified in the same
737 changeset. This flag makes the command
738 inspect unmodified files as candidates for the source of
739 copy. This is a very expensive operation for large
740 projects, so use it with caution. Giving more than one
742 </p>
743 </dd>
745 -D
746 </dt>
748 --irreversible-delete
749 </dt>
750 <dd>
751 <p>
752 Omit the preimage for deletes, i.e. print only the header but not
755 solely for people who want to just concentrate on reviewing the
756 text after the change. In addition, the output obviously lack
757 enough information to apply such a patch in reverse, even manually,
758 hence the name of the option.
759 </p>
760 <div class="paragraph"><p>When used together with <tt>-B</tt>, omit also the preimage in the deletion part
761 of a delete/create pair.</p></div>
762 </dd>
765 </dt>
766 <dd>
767 <p>
769 is the number of potential rename/copy targets. This
770 option prevents rename/copy detection from running if
771 the number of rename/copy targets exceeds the specified
772 number.
773 </p>
774 </dd>
777 </dt>
778 <dd>
779 <p>
780 Output the patch in the order specified in the
782 </p>
783 </dd>
785 -a
786 </dt>
788 --text
789 </dt>
790 <dd>
791 <p>
792 Treat all files as text.
793 </p>
794 </dd>
796 --ignore-space-at-eol
797 </dt>
798 <dd>
799 <p>
800 Ignore changes in whitespace at EOL.
801 </p>
802 </dd>
804 -b
805 </dt>
807 --ignore-space-change
808 </dt>
809 <dd>
810 <p>
811 Ignore changes in amount of whitespace. This ignores whitespace
812 at line end, and considers all other sequences of one or
813 more whitespace characters to be equivalent.
814 </p>
815 </dd>
817 -w
818 </dt>
820 --ignore-all-space
821 </dt>
822 <dd>
823 <p>
824 Ignore whitespace when comparing lines. This ignores
825 differences even if one line has whitespace where the other
826 line has none.
827 </p>
828 </dd>
831 </dt>
832 <dd>
833 <p>
834 Show the context between diff hunks, up to the specified number
835 of lines, thereby fusing hunks that are close to each other.
836 </p>
837 </dd>
839 --ext-diff
840 </dt>
841 <dd>
842 <p>
843 Allow an external diff helper to be executed. If you set an
846 </p>
847 </dd>
849 --no-ext-diff
850 </dt>
851 <dd>
852 <p>
853 Disallow external diff drivers.
854 </p>
855 </dd>
858 </dt>
859 <dd>
860 <p>
863 Using "none" will consider the submodule modified when it either contains
864 untracked or modified files or its HEAD differs from the commit recorded
865 in the superproject and can be used to override any settings of the
866 <em>ignore</em> option in <a href="git-config.html">git-config(1)</a> or <a href="gitmodules.html">gitmodules(5)</a>. When
867 "untracked" is used submodules are not considered dirty when they only
868 contain untracked content (but they are still scanned for modified
869 content). Using "dirty" ignores all changes to the work tree of submodules,
870 only changes to the commits stored in the superproject are shown (this was
872 </p>
873 </dd>
876 </dt>
877 <dd>
878 <p>
879 Show the given source prefix instead of "a/".
880 </p>
881 </dd>
884 </dt>
885 <dd>
886 <p>
887 Show the given destination prefix instead of "b/".
888 </p>
889 </dd>
891 --no-prefix
892 </dt>
893 <dd>
894 <p>
895 Do not show any source or destination prefix.
896 </p>
897 </dd>
898 </dl></div>
904 </dt>
905 <dd>
906 <p>
908 </p>
909 </dd>
912 </dt>
915 </dt>
916 <dd>
917 <p>
919 current working directory.
920 </p>
921 </dd>
923 -n
924 </dt>
926 --numbered
927 </dt>
928 <dd>
929 <p>
931 </p>
932 </dd>
934 -N
935 </dt>
937 --no-numbered
938 </dt>
939 <dd>
940 <p>
942 </p>
943 </dd>
946 </dt>
947 <dd>
948 <p>
950 </p>
951 </dd>
953 --numbered-files
954 </dt>
955 <dd>
956 <p>
957 Output file names will be a simple number sequence
958 without the default first line of the commit appended.
959 </p>
960 </dd>
962 -k
963 </dt>
965 --keep-subject
966 </dt>
967 <dd>
968 <p>
970 commit log message.
971 </p>
972 </dd>
974 -s
975 </dt>
977 --signoff
978 </dt>
979 <dd>
980 <p>
982 the committer identity of yourself.
983 </p>
984 </dd>
986 --stdout
987 </dt>
988 <dd>
989 <p>
990 Print all commits to the standard output in mbox format,
991 instead of creating a file for each one.
992 </p>
993 </dd>
996 </dt>
997 <dd>
998 <p>
999 Create multipart/mixed attachment, the first part of
1000 which is the commit message and the patch itself in the
1002 </p>
1003 </dd>
1005 --no-attach
1006 </dt>
1007 <dd>
1008 <p>
1009 Disable the creation of an attachment, overriding the
1010 configuration setting.
1011 </p>
1012 </dd>
1015 </dt>
1016 <dd>
1017 <p>
1018 Create multipart/mixed attachment, the first part of
1019 which is the commit message and the patch itself in the
1021 </p>
1022 </dd>
1025 </dt>
1027 --no-thread
1028 </dt>
1029 <dd>
1030 <p>
1032 make the second and subsequent mails appear as replies to the
1034 reference.
1035 </p>
1036 <div class="paragraph"><p>The optional <style> argument can be either <tt>shallow</tt> or <tt>deep</tt>.
1038 series, where the head is chosen from the cover letter, the
1040 threading makes every mail a reply to the previous one.</p></div>
1041 <div class="paragraph"><p>The default is <tt>--no-thread</tt>, unless the <em>format.thread</em> configuration
1044 <div class="paragraph"><p>Beware that the default for <em>git send-email</em> is to thread emails
1047 </dd>
1049 --in-reply-to=Message-Id
1050 </dt>
1051 <dd>
1052 <p>
1054 reply to the given Message-Id, which avoids breaking threads to
1055 provide a new patch series.
1056 </p>
1057 </dd>
1059 --ignore-if-in-upstream
1060 </dt>
1061 <dd>
1062 <p>
1063 Do not include a patch that matches a commit in
1066 patches being generated, and any patch that matches is
1067 ignored.
1068 </p>
1069 </dd>
1072 </dt>
1073 <dd>
1074 <p>
1077 allows for useful naming of a patch series, and can be
1079 </p>
1080 </dd>
1083 </dt>
1084 <dd>
1085 <p>
1087 to any configured headers, and may be used multiple times.
1088 </p>
1089 </dd>
1092 </dt>
1093 <dd>
1094 <p>
1096 to any configured headers, and may be used multiple times.
1097 </p>
1098 </dd>
1101 </dt>
1102 <dd>
1103 <p>
1104 Add an arbitrary header to the email headers. This is in addition
1105 to any configured headers, and may be used multiple times.
1107 </p>
1108 </dd>
1110 --cover-letter
1111 </dt>
1112 <dd>
1113 <p>
1114 In addition to the patches, generate a cover letter file
1115 containing the shortlog and the overall diffstat. You can
1116 fill in a description in the file before sending it out.
1117 </p>
1118 </dd>
1121 </dt>
1122 <dd>
1123 <p>
1124 Add a signature to each message produced. Per RFC 3676 the signature
1125 is separated from the body by a line with '-- ' on it. If the
1126 signature option is omitted the signature defaults to the git version
1127 number.
1128 </p>
1129 </dd>
1132 </dt>
1133 <dd>
1134 <p>
1136 filenames, use specified suffix. A common alternative is
1138 suffix.
1139 </p>
1140 <div class="paragraph"><p>Note that the leading character does not have to be a dot; for example,
1141 you can use <tt>--suffix=-patch</tt> to get <tt>0001-description-of-my-change-patch</tt>.</p></div>
1142 </dd>
1144 --quiet
1145 </dt>
1146 <dd>
1147 <p>
1148 Do not print the names of the generated files to standard output.
1149 </p>
1150 </dd>
1152 --no-binary
1153 </dt>
1154 <dd>
1155 <p>
1156 Do not output contents of changes in binary files, instead
1157 display a notice that those files changed. Patches generated
1158 using this option cannot be applied properly, but they are
1159 still useful for code review.
1160 </p>
1161 </dd>
1163 --root
1164 </dt>
1165 <dd>
1166 <p>
1168 is just a single commit (that would normally be treated as a
1170 range are always formatted as creation patches, independently
1171 of this flag.
1172 </p>
1173 </dd>
1174 </dl></div>
1175 </div>
1179 defaults for the subject prefix and file suffix, number patches when
1181 attachments, and sign off patches with configuration variables.</p></div>
1184 <pre><tt>[format]
1185 headers = "Organization: git-foo\n"
1186 subjectprefix = CHANGE
1187 suffix = .txt
1188 numbered = auto
1191 attach [ = mime-boundary-string ]
1192 signoff = true</tt></pre>
1193 </div></div>
1194 </div>
1197 <div class="paragraph"><p>The patch produced by <em>git format-patch</em> is in UNIX mailbox format,
1198 with a fixed "magic" time stamp to indicate that the file is output
1199 from format-patch rather than a real mailbox, like so:</p></div>
1207 MIME-Version: 1.0
1208 Content-Type: text/plain; charset=UTF-8
1209 Content-Transfer-Encoding: 8bit
1211 arch/arm config files were slimmed down using a python script
1212 (See commit c2330e286f68f1c408b4aa6515ba49d57f05beae comment)
1214 Do the same for ia64 so we can have sleek & trim looking
1215 ...</tt></pre>
1216 </div></div>
1217 <div class="paragraph"><p>Typically it will be placed in a MUA’s drafts folder, edited to add
1218 timely commentary that should not go in the changelog after the three
1219 dashes, and then sent as a message whose body, in our example, starts
1220 with "arch/arm config files were…". On the receiving end, readers
1221 can save interesting patches in a UNIX mailbox and apply them with
1223 <div class="paragraph"><p>When a patch is part of an ongoing discussion, the patch generated by
1225 --scissors</em> feature. After your response to the discussion comes a
1226 line that consists solely of "<tt>-- >8 --</tt>" (scissors and perforation),
1227 followed by the patch with unnecessary header fields removed:</p></div>
1230 <pre><tt>...
1231 > So we should do such-and-such.
1233 Makes sense to me. How about this patch?
1236 Subject: [IA64] Put ia64 config files on the Uwe Kleine-König diet
1238 arch/arm config files were slimmed down using a python script
1239 ...</tt></pre>
1240 </div></div>
1242 patch, so in addition to the "<tt>From $SHA1 $magic_timestamp</tt>" marker you
1244 title is likely to be different from the subject of the discussion the
1245 patch is in response to, so it is likely that you would want to keep
1246 the Subject: line, like the example above.</p></div>
1247 <h3 id="_checking_for_patch_corruption">Checking for patch corruption</h3><div style="clear:left"></div>
1248 <div class="paragraph"><p>Many mailers if not set up properly will corrupt whitespace. Here are
1249 two common types of corruption:</p></div>
1251 <li>
1252 <p>
1254 </p>
1255 </li>
1256 <li>
1257 <p>
1258 Non-empty context lines that have one extra whitespace at the
1259 beginning.
1260 </p>
1261 </li>
1262 </ul></div>
1265 <li>
1266 <p>
1267 Send the patch to yourself, exactly the way you would, except
1268 with To: and Cc: lines that do not contain the list and
1269 maintainer address.
1270 </p>
1271 </li>
1272 <li>
1273 <p>
1274 Save that patch to a file in UNIX mailbox format. Call it a.patch,
1275 say.
1276 </p>
1277 </li>
1278 <li>
1279 <p>
1280 Apply it:
1281 </p>
1285 $ git checkout test-apply
1286 $ git reset --hard
1287 $ git am a.patch</tt></pre>
1288 </div></div>
1289 </li>
1290 </ul></div>
1291 <div class="paragraph"><p>If it does not apply correctly, there can be various reasons.</p></div>
1293 <li>
1294 <p>
1296 does not have much to do with your MUA. You might want to rebase
1298 this case.
1299 </p>
1300 </li>
1301 <li>
1302 <p>
1303 The MUA corrupted your patch; "am" would complain that
1304 the patch does not apply. Look in the .git/rebase-apply/ subdirectory and
1306 corruption patterns mentioned above.
1307 </p>
1308 </li>
1309 <li>
1310 <p>
1313 see in the commit log message, it is very likely that the
1314 receiver would end up hand editing the log message when applying
1315 your patch. Things like "Hi, this is my first patch.\n" in the
1316 patch e-mail should come after the three-dash line that signals
1317 the end of the commit message.
1318 </p>
1319 </li>
1320 </ul></div>
1321 </div>
1324 <div class="paragraph"><p>Here are some hints on how to successfully submit patches inline using
1325 various mailers.</p></div>
1328 interface, so it will mangle any emails that you send. You can however
1329 use "git send-email" and send your patches through the GMail SMTP server, or
1330 use any IMAP email client to connect to the google IMAP server and forward
1331 the emails through that.</p></div>
1332 <div class="paragraph"><p>For hints on using <em>git send-email</em> to send your patches through the
1333 GMail SMTP server, see the EXAMPLE section of <a href="git-send-email.html">git-send-email(1)</a>.</p></div>
1339 resulting email unusable by git.</p></div>
1340 <div class="paragraph"><p>There are three different approaches: use an add-on to turn off line wraps,
1341 configure Thunderbird to not mangle patches, or use
1342 an external editor to keep Thunderbird from mangling the patches.</p></div>
1345 <a href="https://addons.mozilla.org/thunderbird/addon/toggle-word-wrap/">https://addons.mozilla.org/thunderbird/addon/toggle-word-wrap/</a>
1347 that you can tick off. Now you can compose the message as you otherwise do
1349 insert line breaks manually in any text that you type.</p></div>
1353 <li>
1354 <p>
1355 Configure your mail server composition as plain text:
1357 uncheck "Compose Messages in HTML".
1358 </p>
1359 </li>
1360 <li>
1361 <p>
1362 Configure your general composition window to not wrap.
1363 </p>
1367 Edit..Preferences..Advanced..Config Editor. Search for
1368 "mail.wrap_long_lines".
1370 </li>
1371 <li>
1372 <p>
1373 Disable the use of format=flowed:
1374 Edit..Preferences..Advanced..Config Editor. Search for
1375 "mailnews.send_plaintext_flowed".
1377 </p>
1378 </li>
1379 </ol></div>
1382 and the patches will not be mangled.</p></div>
1385 AboutConfig from <a href="http://aboutconfig.mozdev.org/">http://aboutconfig.mozdev.org/</a> and
1386 External Editor from <a href="http://globs.org/articles.php?lng=en&pg=8">http://globs.org/articles.php?lng=en&pg=8</a></p></div>
1388 <li>
1389 <p>
1390 Prepare the patch as a text file using your method of choice.
1391 </p>
1392 </li>
1393 <li>
1394 <p>
1395 Before opening a compose window, use Edit→Account Settings to
1396 uncheck the "Compose messages in HTML format" setting in the
1397 "Composition & Addressing" panel of the account to be used to
1398 send the patch.
1399 </p>
1400 </li>
1401 <li>
1402 <p>
1404 window for the patch, use Tools→about:config to set the
1405 following to the indicated values:
1406 </p>
1411 </div></div>
1412 </li>
1413 <li>
1414 <p>
1415 Open a compose window and click the external editor icon.
1416 </p>
1417 </li>
1418 <li>
1419 <p>
1420 In the external editor window, read in the patch file and exit
1421 the editor normally.
1422 </p>
1423 </li>
1424 </ol></div>
1430 mail.identity.default.compose_html => false
1432 </div></div>
1434 you include patches with Thunderbird in an easy way. To use it, do the
1435 steps above and then use the script as the external editor.</p></div>
1439 <li>
1440 <p>
1441 Prepare the patch as a text file.
1442 </p>
1443 </li>
1444 <li>
1445 <p>
1446 Click on New Mail.
1447 </p>
1448 </li>
1449 <li>
1450 <p>
1451 Go under "Options" in the Composer window and be sure that
1452 "Word wrap" is not set.
1453 </p>
1454 </li>
1455 <li>
1456 <p>
1458 </p>
1459 </li>
1460 <li>
1461 <p>
1462 Back in the compose window: add whatever other text you wish to the
1463 message, complete the addressing and subject fields, and press send.
1464 </p>
1465 </li>
1466 </ol></div>
1467 </div>
1471 <li>
1472 <p>
1473 Extract commits between revisions R1 and R2, and apply them on top of
1475 </p>
1479 </div></div>
1480 </li>
1481 <li>
1482 <p>
1483 Extract all commits which are in the current branch but not in the
1484 origin branch:
1485 </p>
1489 </div></div>
1490 <div class="paragraph"><p>For each commit a separate file is created in the current directory.</p></div>
1491 </li>
1492 <li>
1493 <p>
1495 project:
1496 </p>
1500 </div></div>
1501 </li>
1502 <li>
1503 <p>
1504 The same as the previous one:
1505 </p>
1509 </div></div>
1511 intelligently to produce a renaming patch. A renaming patch reduces
1512 the amount of text output, and generally makes it easier to review.
1514 use it only when you know the recipient uses git to apply your patch.</p></div>
1515 </li>
1516 <li>
1517 <p>
1518 Extract three topmost commits from the current branch and format them
1519 as e-mailable patches:
1520 </p>
1524 </div></div>
1525 </li>
1526 </ul></div>
1527 </div>
1530 <div class="paragraph"><p><a href="git-am.html">git-am(1)</a>, <a href="git-send-email.html">git-send-email(1)</a></p></div>
1531 </div>
1535 </div>
1539 </div>
1540 </div>
1541 </body>
1542 </html>