public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Jonathan Haws <Jonathan.Haws@sdl.usu.edu>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] alfred: Externalizing ALFRED_INTERVAL for setting synchronization interval
Date: Thu, 28 Jul 2016 20:18:38 +0200	[thread overview]
Message-ID: <5348242.OI0toffihS@sven-edge> (raw)
In-Reply-To: <1469729158.5505.10.camel@c00941>

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

On Donnerstag, 28. Juli 2016 18:05:59 CEST Jonathan Haws wrote:
> I've never used send-email.  I'll do some digging, learn it, and
> resubmit.

I would recommend to use msmtp to communicate with your remote SMTP server.
More informations can be found [1] when searching for 

    "git send-email" "sendemail.smtpserver" "msmtp"

Btw. you can remove your password from the smtp config (but keep the
"password" line without the "my-secret" part) and msmtp will then ask for each
mail for your password.

The interface of "git send-email" is quite easy. Just specify the name of the
patch files as argument of "git send-email" and then it will handle the sending +
threading for you.

Kind regards,
	Sven

[1] https://git.wiki.kernel.org/index.php/GitTips#Using_msmtp_to_send_your_patches

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-07-28 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 17:19 [B.A.T.M.A.N.] [PATCH] alfred: Externalizing ALFRED_INTERVAL for setting synchronization interval Jonathan Haws
2016-07-28 17:41 ` Sven Eckelmann
     [not found]   ` <1469729158.5505.10.camel@c00941>
2016-07-28 18:18     ` Sven Eckelmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5348242.OI0toffihS@sven-edge \
    --to=sven@narfation.org \
    --cc=Jonathan.Haws@sdl.usu.edu \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox