Skip to content

Commit 540e8ec

Browse files
committed
Merge pull request progit#290 from tessus/master
fixed error in the imap section
2 parents 6f5c55b + 452468e commit 540e8ec

File tree

2 files changed

+32
-3
lines changed

2 files changed

+32
-3
lines changed

book/05-distributed-git/sections/contributing.asc

Lines changed: 26 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -706,7 +706,32 @@ You can set each value separately with a series of `git config` commands, or you
706706
-----
707707

708708
If your IMAP server doesn't use SSL, the last two lines probably aren't necessary, and the host value will be `imap://` instead of `imaps://`.
709-
When that is set up, you can use `git send-email` to place the patch series in the Drafts folder of the specified IMAP server:
709+
When that is set up, you can use `git imap-send` to place the patch series in the Drafts folder of the specified IMAP server:
710+
711+
[source,console]
712+
-----
713+
$ cat *.patch |git imap-send
714+
Resolving imap.gmail.com... ok
715+
Connecting to [74.125.142.109]:993... ok
716+
Logging in...
717+
sending 2 messages
718+
100% (2/2) done
719+
-----
720+
721+
At this point, you should be able to go to your Drafts folder, change the To field to the mailing list you're sending the patch to, possibly CC the maintainer or person responsible for that section, and send it off.
722+
723+
You can also send the patches through an SMTP server. As before, you can set each value separately with a series of `git config` commands, or you can add them manually in the sendemail section in your `~/.gitconfig` file:
724+
725+
[source,ini]
726+
-----
727+
[sendemail]
728+
smtpencryption = tls
729+
smtpserver = smtp.gmail.com
730+
smtpuser = user@gmail.com
731+
smtpserverport = 587
732+
-----
733+
734+
After this is done, you can use `git send-email` to send your patches:
710735

711736
[source,console]
712737
-----
@@ -739,8 +764,6 @@ References: <y>
739764
Result: OK
740765
-----
741766

742-
At this point, you should be able to go to your Drafts folder, change the To field to the mailing list you're sending the patch to, possibly CC the maintainer or person responsible for that section, and send it off.
743-
744767
==== Summary
745768

746769
This section has covered a number of common workflows for dealing with several very different types of Git projects you're likely to encounter, and introduced a couple of new tools to help you manage this process.

book/C-git-commands/1-git-commands.asc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -404,6 +404,12 @@ The `git format-patch` command is used to generate a series of patches in mbox f
404404

405405
We go through an example of contributing to a project using the `git format-patch` tool in <<_project_over_email>>.
406406

407+
==== git imap-send
408+
409+
The `git imap-send` command uploads a mailbox generated with `git format-patch` into an IMAP drafts folder.
410+
411+
We go through an example of contributing to a project by sending patches with the `git imap-send` tool in <<_project_over_email>>.
412+
407413
==== git send-email
408414

409415
The `git send-email` command is used to send patches that are generated with `git format-patch` over email.

0 commit comments

Comments
 (0)