Git development
 help / color / mirror / Atom feed
From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: "Felipe Contreras" <felipe.contreras@gmail.com>,
	git@vger.kernel.org, "Tor Arvid Lund" <torarvid@gmail.com>,
	"Christian Jaeger" <christian@jaeger.mine.nu>
Subject: What do you use to receive mailed patches? (was: What do you use to send git patches?)
Date: Fri, 5 Sep 2008 17:15:44 +0300	[thread overview]
Message-ID: <e29894ca0809050715p6cc11525k7da204b43ae164ee@mail.gmail.com> (raw)

Hi!

Thanks Jakub for your answer.

On Fri, Sep 5, 2008 at 5:10 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>> If somebody could explain how they handle the git send-mail patches
>> they recieve, I would be thankful. How do you create .mbox files? What
>> is your workflow when you deal with mails?
>
> I almost always use git-format-patch to generate patches (some people
> use git-show or git-diff for proof-of-concept patches), and either use
> git-send-email (I have sendmail configured to send mails via GMail,
> but my computer is single-user machine; you can try sendemail.smpt*
> options instead, if you have appropriate Perl modules installed), or
> use KMail: Message > Insert file, ensuring that in Options I have Word
> wrapping turned off.
>
> In some rare case I used 'stg mail' (also via properly configured
> sendmail).
>

My question was about handling the patches you receive. Sending
configuration is quite easy.

Thanks
-- 
Marc-André Lureau

             reply	other threads:[~2008-09-05 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 14:15 Marc-André Lureau [this message]
2008-09-05 14:30 ` What do you use to receive mailed patches? (was: What do you use to send git patches?) Jakub Narebski
2008-09-05 14:33 ` Pieter de Bie

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=e29894ca0809050715p6cc11525k7da204b43ae164ee@mail.gmail.com \
    --to=marcandre.lureau@gmail.com \
    --cc=christian@jaeger.mine.nu \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=torarvid@gmail.com \
    /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