]>
Commit | Line | Data |
---|---|---|
56333bac JS |
1 | Checklist (and a short version for the impatient): |
2 | ||
a7af09d2 JA |
3 | Commits: |
4 | ||
56333bac JS |
5 | - make commits of logical units |
6 | - check for unnecessary whitespace with "git diff --check" | |
7 | before committing | |
8 | - do not check in commented out code or unneeded files | |
56333bac JS |
9 | - the first line of the commit message should be a short |
10 | description and should skip the full stop | |
47afed5d SV |
11 | - the body should provide a meaningful commit message, which: |
12 | - uses the imperative, present tense: "change", | |
13 | not "changed" or "changes". | |
14 | - includes motivation for the change, and contrasts | |
15 | its implementation with previous behaviour | |
56333bac | 16 | - if you want your work included in git.git, add a |
8e7425da | 17 | "Signed-off-by: Your Name <you@example.com>" line to the |
56333bac JS |
18 | commit message (or just use the option "-s" when |
19 | committing) to confirm that you agree to the Developer's | |
20 | Certificate of Origin | |
d3017e93 JS |
21 | - make sure that you have tests for the bug you are fixing |
22 | - make sure that the test suite passes after your commit | |
a7af09d2 JA |
23 | |
24 | Patch: | |
25 | ||
56333bac | 26 | - use "git format-patch -M" to create the patch |
a7af09d2 | 27 | - do not PGP sign your patch |
56333bac JS |
28 | - do not attach your patch, but read in the mail |
29 | body, unless you cannot teach your mailer to | |
30 | leave the formatting of the patch alone. | |
31 | - be careful doing cut & paste into your mailer, not to | |
32 | corrupt whitespaces. | |
33 | - provide additional information (which is unsuitable for | |
34 | the commit message) between the "---" and the diffstat | |
15320175 AR |
35 | - if you change, add, or remove a command line option or |
36 | make some other user interface change, the associated | |
37 | documentation should be updated as well. | |
d3017e93 JS |
38 | - if your name is not writable in ASCII, make sure that |
39 | you send off a message in the correct encoding. | |
13d4e6f7 | 40 | - send the patch to the list (git@vger.kernel.org) and the |
0b059940 JH |
41 | maintainer (gitster@pobox.com) if (and only if) the patch |
42 | is ready for inclusion. If you use git-send-email(1), | |
43 | please test it first by sending email to yourself. | |
56333bac JS |
44 | |
45 | Long version: | |
46 | ||
31408251 JH |
47 | I started reading over the SubmittingPatches document for Linux |
48 | kernel, primarily because I wanted to have a document similar to | |
49 | it for the core GIT to make sure people understand what they are | |
50 | doing when they write "Signed-off-by" line. | |
51 | ||
52 | But the patch submission requirements are a lot more relaxed | |
45d2b286 JH |
53 | here on the technical/contents front, because the core GIT is |
54 | thousand times smaller ;-). So here is only the relevant bits. | |
31408251 JH |
55 | |
56 | ||
57 | (1) Make separate commits for logically separate changes. | |
58 | ||
59 | Unless your patch is really trivial, you should not be sending | |
60 | out a patch that was generated between your working tree and | |
61 | your commit head. Instead, always make a commit with complete | |
62 | commit message and generate a series of patches from your | |
63 | repository. It is a good discipline. | |
64 | ||
65 | Describe the technical detail of the change(s). | |
66 | ||
45d2b286 | 67 | If your description starts to get too long, that's a sign that you |
31408251 | 68 | probably need to split up your commit to finer grained pieces. |
47afed5d SV |
69 | That being said, patches which plainly describe the things that |
70 | help reviewers check the patch, and future maintainers understand | |
71 | the code, are the most beautiful patches. Descriptions that summarise | |
72 | the point in the subject well, and describe the motivation for the | |
73 | change, the approach taken by the change, and if relevant how this | |
74 | differs substantially from the prior version, can be found on Usenet | |
75 | archives back into the late 80's. Consider it like good Netiquette, | |
76 | but for code. | |
31408251 | 77 | |
45d2b286 JH |
78 | Oh, another thing. I am picky about whitespaces. Make sure your |
79 | changes do not trigger errors with the sample pre-commit hook shipped | |
16507fcf BL |
80 | in templates/hooks--pre-commit. To help ensure this does not happen, |
81 | run git diff --check on your changes before you commit. | |
31408251 | 82 | |
31408251 | 83 | |
243bfd33 JS |
84 | (1a) Try to be nice to older C compilers |
85 | ||
8b1d88e8 | 86 | We try to support a wide range of C compilers to compile |
243bfd33 JS |
87 | git with. That means that you should not use C99 initializers, even |
88 | if a lot of compilers grok it. | |
89 | ||
90 | Also, variables have to be declared at the beginning of the block | |
91 | (you can check this with gcc, using the -Wdeclaration-after-statement | |
92 | option). | |
93 | ||
94 | Another thing: NULL pointers shall be written as NULL, not as 0. | |
95 | ||
96 | ||
45d2b286 JH |
97 | (2) Generate your patch using git tools out of your commits. |
98 | ||
99 | git based diff tools (git, Cogito, and StGIT included) generate | |
100 | unidiff which is the preferred format. | |
101 | ||
31408251 JH |
102 | You do not have to be afraid to use -M option to "git diff" or |
103 | "git format-patch", if your patch involves file renames. The | |
104 | receiving end can handle them just fine. | |
105 | ||
106 | Please make sure your patch does not include any extra files | |
107 | which do not belong in a patch submission. Make sure to review | |
108 | your patch after generating it, to ensure accuracy. Before | |
109 | sending out, please make sure it cleanly applies to the "master" | |
45d2b286 JH |
110 | branch head. If you are preparing a work based on "next" branch, |
111 | that is fine, but please mark it as such. | |
31408251 JH |
112 | |
113 | ||
114 | (3) Sending your patches. | |
115 | ||
45d2b286 | 116 | People on the git mailing list need to be able to read and |
31408251 JH |
117 | comment on the changes you are submitting. It is important for |
118 | a developer to be able to "quote" your changes, using standard | |
119 | e-mail tools, so that they may comment on specific portions of | |
addf88e4 | 120 | your code. For this reason, all patches should be submitted |
45d2b286 JH |
121 | "inline". WARNING: Be wary of your MUAs word-wrap |
122 | corrupting your patch. Do not cut-n-paste your patch; you can | |
123 | lose tabs that way if you are not careful. | |
31408251 | 124 | |
45d2b286 | 125 | It is a common convention to prefix your subject line with |
31408251 | 126 | [PATCH]. This lets people easily distinguish patches from other |
4e891acf JH |
127 | e-mail discussions. Use of additional markers after PATCH and |
128 | the closing bracket to mark the nature of the patch is also | |
129 | encouraged. E.g. [PATCH/RFC] is often used when the patch is | |
130 | not ready to be applied but it is for discussion, [PATCH v2], | |
131 | [PATCH v3] etc. are often seen when you are sending an update to | |
132 | what you have previously sent. | |
31408251 JH |
133 | |
134 | "git format-patch" command follows the best current practice to | |
135 | format the body of an e-mail message. At the beginning of the | |
136 | patch should come your commit message, ending with the | |
137 | Signed-off-by: lines, and a line that consists of three dashes, | |
138 | followed by the diffstat information and the patch itself. If | |
139 | you are forwarding a patch from somebody else, optionally, at | |
140 | the beginning of the e-mail message just before the commit | |
141 | message starts, you can put a "From: " line to name that person. | |
142 | ||
143 | You often want to add additional explanation about the patch, | |
144 | other than the commit message itself. Place such "cover letter" | |
145 | material between the three dash lines and the diffstat. | |
146 | ||
147 | Do not attach the patch as a MIME attachment, compressed or not. | |
e30b217b JH |
148 | Do not let your e-mail client send quoted-printable. Do not let |
149 | your e-mail client send format=flowed which would destroy | |
150 | whitespaces in your patches. Many | |
31408251 JH |
151 | popular e-mail applications will not always transmit a MIME |
152 | attachment as plain text, making it impossible to comment on | |
153 | your code. A MIME attachment also takes a bit more time to | |
154 | process. This does not decrease the likelihood of your | |
155 | MIME-attached change being accepted, but it makes it more likely | |
156 | that it will be postponed. | |
157 | ||
158 | Exception: If your mailer is mangling patches then someone may ask | |
9847f7e0 | 159 | you to re-send them using MIME, that is OK. |
31408251 | 160 | |
9847f7e0 JH |
161 | Do not PGP sign your patch, at least for now. Most likely, your |
162 | maintainer or other people on the list would not have your PGP | |
163 | key and would not bother obtaining it anyway. Your patch is not | |
164 | judged by who you are; a good patch from an unknown origin has a | |
165 | far better chance of being accepted than a patch from a known, | |
166 | respected origin that is done poorly or does incorrect things. | |
167 | ||
168 | If you really really really really want to do a PGP signed | |
169 | patch, format it as "multipart/signed", not a text/plain message | |
170 | that starts with '-----BEGIN PGP SIGNED MESSAGE-----'. That is | |
171 | not a text/plain, it's something else. | |
172 | ||
173 | Note that your maintainer does not necessarily read everything | |
174 | on the git mailing list. If your patch is for discussion first, | |
175 | send it "To:" the mailing list, and optionally "cc:" him. If it | |
176 | is trivially correct or after the list reached a consensus, send | |
0b059940 JH |
177 | it "To:" the maintainer and optionally "cc:" the list for |
178 | inclusion. | |
31408251 | 179 | |
04d24455 JH |
180 | Also note that your maintainer does not actively involve himself in |
181 | maintaining what are in contrib/ hierarchy. When you send fixes and | |
182 | enhancements to them, do not forget to "cc: " the person who primarily | |
183 | worked on that hierarchy in contrib/. | |
184 | ||
31408251 | 185 | |
84ab7b6f | 186 | (4) Sign your work |
31408251 JH |
187 | |
188 | To improve tracking of who did what, we've borrowed the | |
189 | "sign-off" procedure from the Linux kernel project on patches | |
190 | that are being emailed around. Although core GIT is a lot | |
191 | smaller project it is a good discipline to follow it. | |
192 | ||
193 | The sign-off is a simple line at the end of the explanation for | |
194 | the patch, which certifies that you wrote it or otherwise have | |
195 | the right to pass it on as a open-source patch. The rules are | |
196 | pretty simple: if you can certify the below: | |
197 | ||
198 | Developer's Certificate of Origin 1.1 | |
199 | ||
200 | By making a contribution to this project, I certify that: | |
201 | ||
202 | (a) The contribution was created in whole or in part by me and I | |
203 | have the right to submit it under the open source license | |
204 | indicated in the file; or | |
205 | ||
206 | (b) The contribution is based upon previous work that, to the best | |
207 | of my knowledge, is covered under an appropriate open source | |
208 | license and I have the right under that license to submit that | |
209 | work with modifications, whether created in whole or in part | |
210 | by me, under the same open source license (unless I am | |
211 | permitted to submit under a different license), as indicated | |
212 | in the file; or | |
213 | ||
214 | (c) The contribution was provided directly to me by some other | |
215 | person who certified (a), (b) or (c) and I have not modified | |
216 | it. | |
217 | ||
218 | (d) I understand and agree that this project and the contribution | |
219 | are public and that a record of the contribution (including all | |
220 | personal information I submit with it, including my sign-off) is | |
221 | maintained indefinitely and may be redistributed consistent with | |
222 | this project or the open source license(s) involved. | |
223 | ||
224 | then you just add a line saying | |
225 | ||
226 | Signed-off-by: Random J Developer <random@developer.example.org> | |
227 | ||
69945602 PC |
228 | This line can be automatically added by git if you run the git-commit |
229 | command with the -s option. | |
230 | ||
c11c3b56 JH |
231 | Notice that you can place your own Signed-off-by: line when |
232 | forwarding somebody else's patch with the above rules for | |
233 | D-C-O. Indeed you are encouraged to do so. Do not forget to | |
234 | place an in-body "From: " line at the beginning to properly attribute | |
235 | the change to its true author (see (2) above). | |
236 | ||
67275247 MV |
237 | Also notice that a real name is used in the Signed-off-by: line. Please |
238 | don't hide your real name. | |
239 | ||
c11c3b56 JH |
240 | Some people also put extra tags at the end. |
241 | ||
242 | "Acked-by:" says that the patch was reviewed by the person who | |
243 | is more familiar with the issues and the area the patch attempts | |
244 | to modify. "Tested-by:" says the patch was tested by the person | |
245 | and found to have the desired effect. | |
9740d289 | 246 | |
a941fb4a JH |
247 | ------------------------------------------------ |
248 | An ideal patch flow | |
249 | ||
250 | Here is an ideal patch flow for this project the current maintainer | |
251 | suggests to the contributors: | |
252 | ||
253 | (0) You come up with an itch. You code it up. | |
254 | ||
255 | (1) Send it to the list and cc people who may need to know about | |
256 | the change. | |
257 | ||
258 | The people who may need to know are the ones whose code you | |
259 | are butchering. These people happen to be the ones who are | |
260 | most likely to be knowledgeable enough to help you, but | |
261 | they have no obligation to help you (i.e. you ask for help, | |
262 | don't demand). "git log -p -- $area_you_are_modifying" would | |
263 | help you find out who they are. | |
264 | ||
265 | (2) You get comments and suggestions for improvements. You may | |
266 | even get them in a "on top of your change" patch form. | |
267 | ||
268 | (3) Polish, refine, and re-send to the list and the people who | |
269 | spend their time to improve your patch. Go back to step (2). | |
270 | ||
271 | (4) The list forms consensus that the last round of your patch is | |
272 | good. Send it to the list and cc the maintainer. | |
273 | ||
274 | (5) A topic branch is created with the patch and is merged to 'next', | |
275 | and cooked further and eventually graduates to 'master'. | |
276 | ||
277 | In any time between the (2)-(3) cycle, the maintainer may pick it up | |
278 | from the list and queue it to 'pu', in order to make it easier for | |
279 | people play with it without having to pick up and apply the patch to | |
280 | their trees themselves. | |
281 | ||
63cb8215 MM |
282 | ------------------------------------------------ |
283 | Know the status of your patch after submission | |
284 | ||
285 | * You can use Git itself to find out when your patch is merged in | |
286 | master. 'git pull --rebase' will automatically skip already-applied | |
287 | patches, and will let you know. This works only if you rebase on top | |
288 | of the branch in which your patch has been merged (i.e. it will not | |
289 | tell you if your patch is merged in pu if you rebase on top of | |
290 | master). | |
291 | ||
292 | * Read the git mailing list, the maintainer regularly posts messages | |
293 | entitled "What's cooking in git.git" and "What's in git.git" giving | |
294 | the status of various proposed changes. | |
295 | ||
9740d289 JH |
296 | ------------------------------------------------ |
297 | MUA specific hints | |
298 | ||
299 | Some of patches I receive or pick up from the list share common | |
300 | patterns of breakage. Please make sure your MUA is set up | |
301 | properly not to corrupt whitespaces. Here are two common ones | |
302 | I have seen: | |
303 | ||
304 | * Empty context lines that do not have _any_ whitespace. | |
305 | ||
306 | * Non empty context lines that have one extra whitespace at the | |
307 | beginning. | |
308 | ||
9847f7e0 JH |
309 | One test you could do yourself if your MUA is set up correctly is: |
310 | ||
311 | * Send the patch to yourself, exactly the way you would, except | |
312 | To: and Cc: lines, which would not contain the list and | |
313 | maintainer address. | |
314 | ||
315 | * Save that patch to a file in UNIX mailbox format. Call it say | |
316 | a.patch. | |
317 | ||
318 | * Try to apply to the tip of the "master" branch from the | |
319 | git.git public repository: | |
320 | ||
321 | $ git fetch http://kernel.org/pub/scm/git/git.git master:test-apply | |
322 | $ git checkout test-apply | |
323 | $ git reset --hard | |
59c8e2cb | 324 | $ git am a.patch |
9847f7e0 JH |
325 | |
326 | If it does not apply correctly, there can be various reasons. | |
327 | ||
328 | * Your patch itself does not apply cleanly. That is _bad_ but | |
329 | does not have much to do with your MUA. Please rebase the | |
330 | patch appropriately. | |
331 | ||
59c8e2cb | 332 | * Your MUA corrupted your patch; "am" would complain that |
51ef1daa | 333 | the patch does not apply. Look at .git/rebase-apply/ subdirectory and |
9847f7e0 JH |
334 | see what 'patch' file contains and check for the common |
335 | corruption patterns mentioned above. | |
336 | ||
337 | * While you are at it, check what are in 'info' and | |
338 | 'final-commit' files as well. If what is in 'final-commit' is | |
339 | not exactly what you would want to see in the commit log | |
340 | message, it is very likely that your maintainer would end up | |
341 | hand editing the log message when he applies your patch. | |
342 | Things like "Hi, this is my first patch.\n", if you really | |
343 | want to put in the patch e-mail, should come after the | |
344 | three-dash line that signals the end of the commit message. | |
345 | ||
9740d289 JH |
346 | |
347 | Pine | |
348 | ---- | |
349 | ||
350 | (Johannes Schindelin) | |
351 | ||
352 | I don't know how many people still use pine, but for those poor | |
353 | souls it may be good to mention that the quell-flowed-text is | |
354 | needed for recent versions. | |
355 | ||
356 | ... the "no-strip-whitespace-before-send" option, too. AFAIK it | |
357 | was introduced in 4.60. | |
358 | ||
359 | (Linus Torvalds) | |
360 | ||
361 | And 4.58 needs at least this. | |
362 | ||
363 | --- | |
364 | diff-tree 8326dd8350be64ac7fc805f6563a1d61ad10d32c (from e886a61f76edf5410573e92e38ce22974f9c40f1) | |
365 | Author: Linus Torvalds <torvalds@g5.osdl.org> | |
366 | Date: Mon Aug 15 17:23:51 2005 -0700 | |
367 | ||
368 | Fix pine whitespace-corruption bug | |
369 | ||
370 | There's no excuse for unconditionally removing whitespace from | |
371 | the pico buffers on close. | |
372 | ||
373 | diff --git a/pico/pico.c b/pico/pico.c | |
374 | --- a/pico/pico.c | |
375 | +++ b/pico/pico.c | |
376 | @@ -219,7 +219,9 @@ PICO *pm; | |
a6080a0a JH |
377 | switch(pico_all_done){ /* prepare for/handle final events */ |
378 | case COMP_EXIT : /* already confirmed */ | |
379 | packheader(); | |
9740d289 | 380 | +#if 0 |
a6080a0a | 381 | stripwhitespace(); |
9740d289 | 382 | +#endif |
a6080a0a JH |
383 | c |= COMP_EXIT; |
384 | break; | |
385 | ||
9740d289 | 386 | |
1eb446fa JH |
387 | (Daniel Barkalow) |
388 | ||
389 | > A patch to SubmittingPatches, MUA specific help section for | |
390 | > users of Pine 4.63 would be very much appreciated. | |
391 | ||
392 | Ah, it looks like a recent version changed the default behavior to do the | |
393 | right thing, and inverted the sense of the configuration option. (Either | |
394 | that or Gentoo did it.) So you need to set the | |
395 | "no-strip-whitespace-before-send" option, unless the option you have is | |
396 | "strip-whitespace-before-send", in which case you should avoid checking | |
397 | it. | |
398 | ||
9740d289 JH |
399 | |
400 | Thunderbird | |
401 | ----------- | |
402 | ||
403 | (A Large Angry SCM) | |
404 | ||
1a526d48 JW |
405 | By default, Thunderbird will both wrap emails as well as flag them as |
406 | being 'format=flowed', both of which will make the resulting email unusable | |
407 | by git. | |
408 | ||
9740d289 | 409 | Here are some hints on how to successfully submit patches inline using |
cf6de18a | 410 | Thunderbird. |
9740d289 | 411 | |
1a526d48 JW |
412 | There are two different approaches. One approach is to configure |
413 | Thunderbird to not mangle patches. The second approach is to use | |
414 | an external editor to keep Thunderbird from mangling the patches. | |
415 | ||
416 | Approach #1 (configuration): | |
417 | ||
418 | This recipe is current as of Thunderbird 2.0.0.19. Three steps: | |
419 | 1. Configure your mail server composition as plain text | |
420 | Edit...Account Settings...Composition & Addressing, | |
421 | uncheck 'Compose Messages in HTML'. | |
422 | 2. Configure your general composition window to not wrap | |
423 | Edit..Preferences..Composition, wrap plain text messages at 0 | |
424 | 3. Disable the use of format=flowed | |
425 | Edit..Preferences..Advanced..Config Editor. Search for: | |
426 | mailnews.send_plaintext_flowed | |
427 | toggle it to make sure it is set to 'false'. | |
428 | ||
429 | After that is done, you should be able to compose email as you | |
430 | otherwise would (cut + paste, git-format-patch | git-imap-send, etc), | |
431 | and the patches should not be mangled. | |
432 | ||
433 | Approach #2 (external editor): | |
434 | ||
9740d289 JH |
435 | This recipe appears to work with the current [*1*] Thunderbird from Suse. |
436 | ||
437 | The following Thunderbird extensions are needed: | |
438 | AboutConfig 0.5 | |
439 | http://aboutconfig.mozdev.org/ | |
ff62b7f3 LS |
440 | External Editor 0.7.2 |
441 | http://globs.org/articles.php?lng=en&pg=8 | |
9740d289 JH |
442 | |
443 | 1) Prepare the patch as a text file using your method of choice. | |
444 | ||
445 | 2) Before opening a compose window, use Edit->Account Settings to | |
446 | uncheck the "Compose messages in HTML format" setting in the | |
447 | "Composition & Addressing" panel of the account to be used to send the | |
448 | patch. [*2*] | |
449 | ||
450 | 3) In the main Thunderbird window, _before_ you open the compose window | |
451 | for the patch, use Tools->about:config to set the following to the | |
452 | indicated values: | |
453 | mailnews.send_plaintext_flowed => false | |
cf6de18a | 454 | mailnews.wraplength => 0 |
9740d289 JH |
455 | |
456 | 4) Open a compose window and click the external editor icon. | |
457 | ||
458 | 5) In the external editor window, read in the patch file and exit the | |
459 | editor normally. | |
460 | ||
461 | 6) Back in the compose window: Add whatever other text you wish to the | |
462 | message, complete the addressing and subject fields, and press send. | |
463 | ||
464 | 7) Optionally, undo the about:config/account settings changes made in | |
465 | steps 2 & 3. | |
466 | ||
467 | ||
468 | [Footnotes] | |
469 | *1* Version 1.0 (20041207) from the MozillaThunderbird-1.0-5 rpm of Suse | |
470 | 9.3 professional updates. | |
471 | ||
472 | *2* It may be possible to do this with about:config and the following | |
473 | settings but I haven't tried, yet. | |
474 | mail.html_compose => false | |
475 | mail.identity.default.compose_html => false | |
476 | mail.identity.id?.compose_html => false | |
477 | ||
0c3d26d2 LS |
478 | (Lukas Sandström) |
479 | ||
480 | There is a script in contrib/thunderbird-patch-inline which can help | |
481 | you include patches with Thunderbird in an easy way. To use it, do the | |
482 | steps above and then use the script as the external editor. | |
e30b217b | 483 | |
e30b217b JH |
484 | Gnus |
485 | ---- | |
486 | ||
487 | '|' in the *Summary* buffer can be used to pipe the current | |
488 | message to an external program, and this is a handy way to drive | |
489 | "git am". However, if the message is MIME encoded, what is | |
490 | piped into the program is the representation you see in your | |
491 | *Article* buffer after unwrapping MIME. This is often not what | |
492 | you would want for two reasons. It tends to screw up non ASCII | |
493 | characters (most notably in people's names), and also | |
494 | whitespaces (fatal in patches). Running 'C-u g' to display the | |
495 | message in raw form before using '|' to run the pipe can work | |
496 | this problem around. | |
497 | ||
451fd65a MB |
498 | |
499 | KMail | |
500 | ----- | |
501 | ||
502 | This should help you to submit patches inline using KMail. | |
503 | ||
504 | 1) Prepare the patch as a text file. | |
505 | ||
506 | 2) Click on New Mail. | |
507 | ||
508 | 3) Go under "Options" in the Composer window and be sure that | |
509 | "Word wrap" is not set. | |
510 | ||
511 | 4) Use Message -> Insert file... and insert the patch. | |
512 | ||
513 | 5) Back in the compose window: add whatever other text you wish to the | |
514 | message, complete the addressing and subject fields, and press send. | |
c2163c6a TPW |
515 | |
516 | ||
517 | Gmail | |
518 | ----- | |
519 | ||
50dffd4e JT |
520 | GMail does not appear to have any way to turn off line wrapping in the web |
521 | interface, so this will mangle any emails that you send. You can however | |
522 | use any IMAP email client to connect to the google imap server, and forward | |
df5753c4 | 523 | the emails through that. |
50dffd4e | 524 | |
df5753c4 | 525 | To submit using the IMAP interface, first, edit your ~/.gitconfig to specify your |
c2163c6a TPW |
526 | account settings: |
527 | ||
528 | [imap] | |
529 | folder = "[Gmail]/Drafts" | |
530 | host = imaps://imap.gmail.com | |
531 | user = user@gmail.com | |
532 | pass = p4ssw0rd | |
533 | port = 993 | |
534 | sslverify = false | |
535 | ||
50dffd4e JT |
536 | You might need to instead use: folder = "[Google Mail]/Drafts" if you get an error |
537 | that the "Folder doesn't exist". | |
538 | ||
df5753c4 JH |
539 | Once your commits are ready to be sent to the mailing list, run the |
540 | following command to send the patch emails to your Gmail Drafts | |
541 | folder. | |
c2163c6a | 542 | |
df5753c4 | 543 | $ git format-patch --cover-letter -M --stdout origin/master | git imap-send |
c2163c6a | 544 | |
df5753c4 JH |
545 | Just make sure to disable line wrapping in the email client (GMail web |
546 | interface will line wrap no matter what, so you need to use a real | |
547 | IMAP client). | |
c2163c6a | 548 | |
df5753c4 JH |
549 | Alternatively, you can use "git send-email" and send your patches |
550 | through the GMail SMTP server. edit ~/.gitconfig to specify your | |
551 | account settings: | |
552 | ||
553 | [sendemail] | |
554 | smtpencryption = tls | |
555 | smtpserver = smtp.gmail.com | |
556 | smtpuser = user@gmail.com | |
557 | smtppass = p4ssw0rd | |
558 | smtpserverport = 587 | |
559 | ||
560 | Once your commits are ready to be sent to the mailing list, run the | |
561 | following commands: | |
50dffd4e | 562 | |
df5753c4 JH |
563 | $ git format-patch --cover-letter -M origin/master -o outgoing/ |
564 | $ git send-email outgoing/* |