forked from progit/progit2
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request progit#290 from tessus/master
fixed error in the imap section
- Loading branch information
Showing
2 changed files
with
32 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -706,7 +706,32 @@ You can set each value separately with a series of `git config` commands, or you | |
----- | ||
|
||
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://`. | ||
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: | ||
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: | ||
|
||
[source,console] | ||
----- | ||
$ cat *.patch |git imap-send | ||
Resolving imap.gmail.com... ok | ||
Connecting to [74.125.142.109]:993... ok | ||
Logging in... | ||
sending 2 messages | ||
100% (2/2) done | ||
----- | ||
|
||
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. | ||
|
||
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: | ||
|
||
[source,ini] | ||
----- | ||
[sendemail] | ||
smtpencryption = tls | ||
smtpserver = smtp.gmail.com | ||
smtpuser = [email protected] | ||
smtpserverport = 587 | ||
----- | ||
|
||
After this is done, you can use `git send-email` to send your patches: | ||
|
||
[source,console] | ||
----- | ||
|
@@ -739,8 +764,6 @@ References: <y> | |
Result: OK | ||
----- | ||
|
||
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. | ||
|
||
==== Summary | ||
|
||
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. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters