| blob | 3d3606c2557c881c01dee229a9e0e1f53c06a8f0 |
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.
526 </p>
527 <div class="paragraph"><p>These parameters can also be set individually with <tt>--stat-width=<width></tt>,
528 <tt>--stat-name-width=<name-width></tt> and <tt>--stat-count=<count></tt>.</p></div>
529 </dd>
531 --numstat
532 </dt>
533 <dd>
534 <p>
536 deleted lines in decimal notation and pathname without
537 abbreviation, to make it more machine friendly. For
540 </p>
541 </dd>
543 --shortstat
544 </dt>
545 <dd>
546 <p>
548 number of modified files, as well as number of added and deleted
549 lines.
550 </p>
551 </dd>
554 </dt>
555 <dd>
556 <p>
557 Output the distribution of relative amount of changes for each
559 passing it a comma separated list of parameters.
562 The following parameters are available:
563 </p>
567 </dt>
568 <dd>
569 <p>
570 Compute the dirstat numbers by counting the lines that have been
571 removed from the source, or added to the destination. This ignores
572 the amount of pure code movements within a file. In other words,
573 rearranging lines in a file is not counted as much as other changes.
574 This is the default behavior when no parameter is given.
575 </p>
576 </dd>
579 </dt>
580 <dd>
581 <p>
582 Compute the dirstat numbers by doing the regular line-based diff
583 analysis, and summing the removed/added line counts. (For binary
584 files, count 64-byte chunks instead, since binary files have no
587 lines within a file as much as other changes. The resulting output
589 </p>
590 </dd>
593 </dt>
594 <dd>
595 <p>
596 Compute the dirstat numbers by counting the number of files changed.
597 Each changed file counts equally in the dirstat analysis. This is
599 not have to look at the file contents at all.
600 </p>
601 </dd>
604 </dt>
605 <dd>
606 <p>
607 Count changes in a child directory for the parent directory as well.
609 reported may exceed 100%. The default (non-cumulative) behavior can
611 </p>
612 </dd>
615 </dt>
616 <dd>
617 <p>
618 An integer parameter specifies a cut-off percent (3% by default).
619 Directories contributing less than this percentage of the changes
620 are not shown in the output.
621 </p>
622 </dd>
623 </dl></div>
625 directories with less than 10% of the total amount of changed files,
626 and accumulating child directory counts in the parent directories:
628 </dd>
630 --summary
631 </dt>
632 <dd>
633 <p>
634 Output a condensed summary of extended header information
635 such as creations, renames and mode changes.
636 </p>
637 </dd>
639 --no-renames
640 </dt>
641 <dd>
642 <p>
643 Turn off rename detection, even when the configuration
644 file gives the default to do so.
645 </p>
646 </dd>
648 --full-index
649 </dt>
650 <dd>
651 <p>
652 Instead of the first handful of characters, show the full
653 pre- and post-image blob object names on the "index"
654 line when generating patch format output.
655 </p>
656 </dd>
658 --binary
659 </dt>
660 <dd>
661 <p>
664 </p>
665 </dd>
668 </dt>
669 <dd>
670 <p>
671 Instead of showing the full 40-byte hexadecimal object
672 name in diff-raw format output and diff-tree header
673 lines, show only a partial prefix. This is
675 the diff-patch output format. Non default number of
677 </p>
678 </dd>
681 </dt>
684 </dt>
685 <dd>
686 <p>
687 Break complete rewrite changes into pairs of delete and
688 create. This serves two purposes:
689 </p>
691 not as a series of deletion and insertion mixed together with a very
692 few lines that happen to match textually as the context, but as a
693 single deletion of everything old followed by a single insertion of
696 original should remain in the result for git to consider it a total
697 rewrite (i.e. otherwise the resulting patch will be a series of
698 deletion and insertion mixed together with context lines).</p></div>
700 source of a rename (usually -M only considers a file that disappeared
704 eligible for being picked up as a possible source of a rename to
705 another file.</p></div>
706 </dd>
709 </dt>
712 </dt>
713 <dd>
714 <p>
715 Detect renames.
717 index (i.e. amount of addition/deletions compared to the
719 delete/add pair to be a rename if more than 90% of the file
720 hasn’t changed.
721 </p>
722 </dd>
725 </dt>
728 </dt>
729 <dd>
730 <p>
733 </p>
734 </dd>
736 --find-copies-harder
737 </dt>
738 <dd>
739 <p>
741 if the original file of the copy was modified in the same
742 changeset. This flag makes the command
743 inspect unmodified files as candidates for the source of
744 copy. This is a very expensive operation for large
745 projects, so use it with caution. Giving more than one
747 </p>
748 </dd>
750 -D
751 </dt>
753 --irreversible-delete
754 </dt>
755 <dd>
756 <p>
757 Omit the preimage for deletes, i.e. print only the header but not
760 solely for people who want to just concentrate on reviewing the
761 text after the change. In addition, the output obviously lack
762 enough information to apply such a patch in reverse, even manually,
763 hence the name of the option.
764 </p>
765 <div class="paragraph"><p>When used together with <tt>-B</tt>, omit also the preimage in the deletion part
766 of a delete/create pair.</p></div>
767 </dd>
770 </dt>
771 <dd>
772 <p>
774 is the number of potential rename/copy targets. This
775 option prevents rename/copy detection from running if
776 the number of rename/copy targets exceeds the specified
777 number.
778 </p>
779 </dd>
782 </dt>
783 <dd>
784 <p>
785 Output the patch in the order specified in the
787 </p>
788 </dd>
790 -a
791 </dt>
793 --text
794 </dt>
795 <dd>
796 <p>
797 Treat all files as text.
798 </p>
799 </dd>
801 --ignore-space-at-eol
802 </dt>
803 <dd>
804 <p>
805 Ignore changes in whitespace at EOL.
806 </p>
807 </dd>
809 -b
810 </dt>
812 --ignore-space-change
813 </dt>
814 <dd>
815 <p>
816 Ignore changes in amount of whitespace. This ignores whitespace
817 at line end, and considers all other sequences of one or
818 more whitespace characters to be equivalent.
819 </p>
820 </dd>
822 -w
823 </dt>
825 --ignore-all-space
826 </dt>
827 <dd>
828 <p>
829 Ignore whitespace when comparing lines. This ignores
830 differences even if one line has whitespace where the other
831 line has none.
832 </p>
833 </dd>
836 </dt>
837 <dd>
838 <p>
839 Show the context between diff hunks, up to the specified number
840 of lines, thereby fusing hunks that are close to each other.
841 </p>
842 </dd>
844 --ext-diff
845 </dt>
846 <dd>
847 <p>
848 Allow an external diff helper to be executed. If you set an
851 </p>
852 </dd>
854 --no-ext-diff
855 </dt>
856 <dd>
857 <p>
858 Disallow external diff drivers.
859 </p>
860 </dd>
862 --textconv
863 </dt>
865 --no-textconv
866 </dt>
867 <dd>
868 <p>
869 Allow (or disallow) external text conversion filters to be run
871 details. Because textconv filters are typically a one-way
872 conversion, the resulting diff is suitable for human
873 consumption, but cannot be applied. For this reason, textconv
875 <a href="git-log.html">git-log(1)</a>, but not for <a href="git-format-patch.html">git-format-patch(1)</a> or
876 diff plumbing commands.
877 </p>
878 </dd>
881 </dt>
882 <dd>
883 <p>
886 Using "none" will consider the submodule modified when it either contains
887 untracked or modified files or its HEAD differs from the commit recorded
888 in the superproject and can be used to override any settings of the
889 <em>ignore</em> option in <a href="git-config.html">git-config(1)</a> or <a href="gitmodules.html">gitmodules(5)</a>. When
890 "untracked" is used submodules are not considered dirty when they only
891 contain untracked content (but they are still scanned for modified
892 content). Using "dirty" ignores all changes to the work tree of submodules,
893 only changes to the commits stored in the superproject are shown (this was
895 </p>
896 </dd>
899 </dt>
900 <dd>
901 <p>
902 Show the given source prefix instead of "a/".
903 </p>
904 </dd>
907 </dt>
908 <dd>
909 <p>
910 Show the given destination prefix instead of "b/".
911 </p>
912 </dd>
914 --no-prefix
915 </dt>
916 <dd>
917 <p>
918 Do not show any source or destination prefix.
919 </p>
920 </dd>
921 </dl></div>
927 </dt>
928 <dd>
929 <p>
931 </p>
932 </dd>
935 </dt>
938 </dt>
939 <dd>
940 <p>
942 current working directory.
943 </p>
944 </dd>
946 -n
947 </dt>
949 --numbered
950 </dt>
951 <dd>
952 <p>
954 </p>
955 </dd>
957 -N
958 </dt>
960 --no-numbered
961 </dt>
962 <dd>
963 <p>
965 </p>
966 </dd>
969 </dt>
970 <dd>
971 <p>
973 </p>
974 </dd>
976 --numbered-files
977 </dt>
978 <dd>
979 <p>
980 Output file names will be a simple number sequence
981 without the default first line of the commit appended.
982 </p>
983 </dd>
985 -k
986 </dt>
988 --keep-subject
989 </dt>
990 <dd>
991 <p>
993 commit log message.
994 </p>
995 </dd>
997 -s
998 </dt>
1000 --signoff
1001 </dt>
1002 <dd>
1003 <p>
1005 the committer identity of yourself.
1006 </p>
1007 </dd>
1009 --stdout
1010 </dt>
1011 <dd>
1012 <p>
1013 Print all commits to the standard output in mbox format,
1014 instead of creating a file for each one.
1015 </p>
1016 </dd>
1019 </dt>
1020 <dd>
1021 <p>
1022 Create multipart/mixed attachment, the first part of
1023 which is the commit message and the patch itself in the
1025 </p>
1026 </dd>
1028 --no-attach
1029 </dt>
1030 <dd>
1031 <p>
1032 Disable the creation of an attachment, overriding the
1033 configuration setting.
1034 </p>
1035 </dd>
1038 </dt>
1039 <dd>
1040 <p>
1041 Create multipart/mixed attachment, the first part of
1042 which is the commit message and the patch itself in the
1044 </p>
1045 </dd>
1048 </dt>
1050 --no-thread
1051 </dt>
1052 <dd>
1053 <p>
1055 make the second and subsequent mails appear as replies to the
1057 reference.
1058 </p>
1059 <div class="paragraph"><p>The optional <style> argument can be either <tt>shallow</tt> or <tt>deep</tt>.
1061 series, where the head is chosen from the cover letter, the
1063 threading makes every mail a reply to the previous one.</p></div>
1064 <div class="paragraph"><p>The default is <tt>--no-thread</tt>, unless the <em>format.thread</em> configuration
1067 <div class="paragraph"><p>Beware that the default for <em>git send-email</em> is to thread emails
1070 </dd>
1072 --in-reply-to=Message-Id
1073 </dt>
1074 <dd>
1075 <p>
1077 reply to the given Message-Id, which avoids breaking threads to
1078 provide a new patch series.
1079 </p>
1080 </dd>
1082 --ignore-if-in-upstream
1083 </dt>
1084 <dd>
1085 <p>
1086 Do not include a patch that matches a commit in
1089 patches being generated, and any patch that matches is
1090 ignored.
1091 </p>
1092 </dd>
1095 </dt>
1096 <dd>
1097 <p>
1100 allows for useful naming of a patch series, and can be
1102 </p>
1103 </dd>
1106 </dt>
1107 <dd>
1108 <p>
1110 to any configured headers, and may be used multiple times.
1111 </p>
1112 </dd>
1115 </dt>
1116 <dd>
1117 <p>
1119 to any configured headers, and may be used multiple times.
1120 </p>
1121 </dd>
1124 </dt>
1125 <dd>
1126 <p>
1127 Add an arbitrary header to the email headers. This is in addition
1128 to any configured headers, and may be used multiple times.
1130 </p>
1131 </dd>
1133 --cover-letter
1134 </dt>
1135 <dd>
1136 <p>
1137 In addition to the patches, generate a cover letter file
1138 containing the shortlog and the overall diffstat. You can
1139 fill in a description in the file before sending it out.
1140 </p>
1141 </dd>
1144 </dt>
1145 <dd>
1146 <p>
1147 Add a signature to each message produced. Per RFC 3676 the signature
1148 is separated from the body by a line with '-- ' on it. If the
1149 signature option is omitted the signature defaults to the git version
1150 number.
1151 </p>
1152 </dd>
1155 </dt>
1156 <dd>
1157 <p>
1159 filenames, use specified suffix. A common alternative is
1161 suffix.
1162 </p>
1163 <div class="paragraph"><p>Note that the leading character does not have to be a dot; for example,
1164 you can use <tt>--suffix=-patch</tt> to get <tt>0001-description-of-my-change-patch</tt>.</p></div>
1165 </dd>
1167 --quiet
1168 </dt>
1169 <dd>
1170 <p>
1171 Do not print the names of the generated files to standard output.
1172 </p>
1173 </dd>
1175 --no-binary
1176 </dt>
1177 <dd>
1178 <p>
1179 Do not output contents of changes in binary files, instead
1180 display a notice that those files changed. Patches generated
1181 using this option cannot be applied properly, but they are
1182 still useful for code review.
1183 </p>
1184 </dd>
1186 --root
1187 </dt>
1188 <dd>
1189 <p>
1191 is just a single commit (that would normally be treated as a
1193 range are always formatted as creation patches, independently
1194 of this flag.
1195 </p>
1196 </dd>
1197 </dl></div>
1198 </div>
1202 defaults for the subject prefix and file suffix, number patches when
1204 attachments, and sign off patches with configuration variables.</p></div>
1207 <pre><tt>[format]
1208 headers = "Organization: git-foo\n"
1209 subjectprefix = CHANGE
1210 suffix = .txt
1211 numbered = auto
1214 attach [ = mime-boundary-string ]
1215 signoff = true</tt></pre>
1216 </div></div>
1217 </div>
1220 <div class="paragraph"><p>The patch produced by <em>git format-patch</em> is in UNIX mailbox format,
1221 with a fixed "magic" time stamp to indicate that the file is output
1222 from format-patch rather than a real mailbox, like so:</p></div>
1230 MIME-Version: 1.0
1231 Content-Type: text/plain; charset=UTF-8
1232 Content-Transfer-Encoding: 8bit
1234 arch/arm config files were slimmed down using a python script
1235 (See commit c2330e286f68f1c408b4aa6515ba49d57f05beae comment)
1237 Do the same for ia64 so we can have sleek & trim looking
1238 ...</tt></pre>
1239 </div></div>
1240 <div class="paragraph"><p>Typically it will be placed in a MUA’s drafts folder, edited to add
1241 timely commentary that should not go in the changelog after the three
1242 dashes, and then sent as a message whose body, in our example, starts
1243 with "arch/arm config files were…". On the receiving end, readers
1244 can save interesting patches in a UNIX mailbox and apply them with
1246 <div class="paragraph"><p>When a patch is part of an ongoing discussion, the patch generated by
1248 --scissors</em> feature. After your response to the discussion comes a
1249 line that consists solely of "<tt>-- >8 --</tt>" (scissors and perforation),
1250 followed by the patch with unnecessary header fields removed:</p></div>
1253 <pre><tt>...
1254 > So we should do such-and-such.
1256 Makes sense to me. How about this patch?
1259 Subject: [IA64] Put ia64 config files on the Uwe Kleine-König diet
1261 arch/arm config files were slimmed down using a python script
1262 ...</tt></pre>
1263 </div></div>
1265 patch, so in addition to the "<tt>From $SHA1 $magic_timestamp</tt>" marker you
1267 title is likely to be different from the subject of the discussion the
1268 patch is in response to, so it is likely that you would want to keep
1269 the Subject: line, like the example above.</p></div>
1270 <h3 id="_checking_for_patch_corruption">Checking for patch corruption</h3><div style="clear:left"></div>
1271 <div class="paragraph"><p>Many mailers if not set up properly will corrupt whitespace. Here are
1272 two common types of corruption:</p></div>
1274 <li>
1275 <p>
1277 </p>
1278 </li>
1279 <li>
1280 <p>
1281 Non-empty context lines that have one extra whitespace at the
1282 beginning.
1283 </p>
1284 </li>
1285 </ul></div>
1288 <li>
1289 <p>
1290 Send the patch to yourself, exactly the way you would, except
1291 with To: and Cc: lines that do not contain the list and
1292 maintainer address.
1293 </p>
1294 </li>
1295 <li>
1296 <p>
1297 Save that patch to a file in UNIX mailbox format. Call it a.patch,
1298 say.
1299 </p>
1300 </li>
1301 <li>
1302 <p>
1303 Apply it:
1304 </p>
1308 $ git checkout test-apply
1309 $ git reset --hard
1310 $ git am a.patch</tt></pre>
1311 </div></div>
1312 </li>
1313 </ul></div>
1314 <div class="paragraph"><p>If it does not apply correctly, there can be various reasons.</p></div>
1316 <li>
1317 <p>
1319 does not have much to do with your MUA. You might want to rebase
1321 this case.
1322 </p>
1323 </li>
1324 <li>
1325 <p>
1326 The MUA corrupted your patch; "am" would complain that
1327 the patch does not apply. Look in the .git/rebase-apply/ subdirectory and
1329 corruption patterns mentioned above.
1330 </p>
1331 </li>
1332 <li>
1333 <p>
1336 see in the commit log message, it is very likely that the
1337 receiver would end up hand editing the log message when applying
1338 your patch. Things like "Hi, this is my first patch.\n" in the
1339 patch e-mail should come after the three-dash line that signals
1340 the end of the commit message.
1341 </p>
1342 </li>
1343 </ul></div>
1344 </div>
1347 <div class="paragraph"><p>Here are some hints on how to successfully submit patches inline using
1348 various mailers.</p></div>
1351 interface, so it will mangle any emails that you send. You can however
1352 use "git send-email" and send your patches through the GMail SMTP server, or
1353 use any IMAP email client to connect to the google IMAP server and forward
1354 the emails through that.</p></div>
1355 <div class="paragraph"><p>For hints on using <em>git send-email</em> to send your patches through the
1356 GMail SMTP server, see the EXAMPLE section of <a href="git-send-email.html">git-send-email(1)</a>.</p></div>
1362 resulting email unusable by git.</p></div>
1363 <div class="paragraph"><p>There are three different approaches: use an add-on to turn off line wraps,
1364 configure Thunderbird to not mangle patches, or use
1365 an external editor to keep Thunderbird from mangling the patches.</p></div>
1368 <a href="https://addons.mozilla.org/thunderbird/addon/toggle-word-wrap/">https://addons.mozilla.org/thunderbird/addon/toggle-word-wrap/</a>
1370 that you can tick off. Now you can compose the message as you otherwise do
1372 insert line breaks manually in any text that you type.</p></div>
1376 <li>
1377 <p>
1378 Configure your mail server composition as plain text:
1380 uncheck "Compose Messages in HTML".
1381 </p>
1382 </li>
1383 <li>
1384 <p>
1385 Configure your general composition window to not wrap.
1386 </p>
1390 Edit..Preferences..Advanced..Config Editor. Search for
1391 "mail.wrap_long_lines".
1393 </li>
1394 <li>
1395 <p>
1396 Disable the use of format=flowed:
1397 Edit..Preferences..Advanced..Config Editor. Search for
1398 "mailnews.send_plaintext_flowed".
1400 </p>
1401 </li>
1402 </ol></div>
1405 and the patches will not be mangled.</p></div>
1408 AboutConfig from <a href="http://aboutconfig.mozdev.org/">http://aboutconfig.mozdev.org/</a> and
1409 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>
1411 <li>
1412 <p>
1413 Prepare the patch as a text file using your method of choice.
1414 </p>
1415 </li>
1416 <li>
1417 <p>
1418 Before opening a compose window, use Edit→Account Settings to
1419 uncheck the "Compose messages in HTML format" setting in the
1420 "Composition & Addressing" panel of the account to be used to
1421 send the patch.
1422 </p>
1423 </li>
1424 <li>
1425 <p>
1427 window for the patch, use Tools→about:config to set the
1428 following to the indicated values:
1429 </p>
1434 </div></div>
1435 </li>
1436 <li>
1437 <p>
1438 Open a compose window and click the external editor icon.
1439 </p>
1440 </li>
1441 <li>
1442 <p>
1443 In the external editor window, read in the patch file and exit
1444 the editor normally.
1445 </p>
1446 </li>
1447 </ol></div>
1453 mail.identity.default.compose_html => false
1455 </div></div>
1457 you include patches with Thunderbird in an easy way. To use it, do the
1458 steps above and then use the script as the external editor.</p></div>
1462 <li>
1463 <p>
1464 Prepare the patch as a text file.
1465 </p>
1466 </li>
1467 <li>
1468 <p>
1469 Click on New Mail.
1470 </p>
1471 </li>
1472 <li>
1473 <p>
1474 Go under "Options" in the Composer window and be sure that
1475 "Word wrap" is not set.
1476 </p>
1477 </li>
1478 <li>
1479 <p>
1481 </p>
1482 </li>
1483 <li>
1484 <p>
1485 Back in the compose window: add whatever other text you wish to the
1486 message, complete the addressing and subject fields, and press send.
1487 </p>
1488 </li>
1489 </ol></div>
1490 </div>
1494 <li>
1495 <p>
1496 Extract commits between revisions R1 and R2, and apply them on top of
1498 </p>
1502 </div></div>
1503 </li>
1504 <li>
1505 <p>
1506 Extract all commits which are in the current branch but not in the
1507 origin branch:
1508 </p>
1512 </div></div>
1513 <div class="paragraph"><p>For each commit a separate file is created in the current directory.</p></div>
1514 </li>
1515 <li>
1516 <p>
1518 project:
1519 </p>
1523 </div></div>
1524 </li>
1525 <li>
1526 <p>
1527 The same as the previous one:
1528 </p>
1532 </div></div>
1534 intelligently to produce a renaming patch. A renaming patch reduces
1535 the amount of text output, and generally makes it easier to review.
1537 use it only when you know the recipient uses git to apply your patch.</p></div>
1538 </li>
1539 <li>
1540 <p>
1541 Extract three topmost commits from the current branch and format them
1542 as e-mailable patches:
1543 </p>
1547 </div></div>
1548 </li>
1549 </ul></div>
1550 </div>
1553 <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>
1554 </div>
1558 </div>
1562 </div>
1563 </div>
1564 </body>
1565 </html>