From: Jakub Narebski <jnareb@gmail.com>
To: "Marc-André Lureau" <marcandre.lureau@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 send git patches? (was: [ANNOUNCE] Git User's Survey 2008)
Date: Fri, 05 Sep 2008 07:10:45 -0700 (PDT) [thread overview]
Message-ID: <m3d4jipttz.fsf_-_@localhost.localdomain> (raw)
In-Reply-To: <e29894ca0809050646g2f198890le2312d065696d1dd@mail.gmail.com>
"Marc-André Lureau" <marcandre.lureau@gmail.com> writes:
> May I suggest to add a question next year: which email client do you
> use to handle git attachements (if you do) ?
>
> I cannot find yet a good workflow with either mutt, gmail or evolution
> over imap.
>
> 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).
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-09-05 14:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 21:29 [ANNOUNCE] Git User's Survey 2008 Jakub Narebski
2008-09-01 5:13 ` Scott Chacon
2008-09-01 7:10 ` Felipe Contreras
2008-09-01 7:18 ` David John
2008-09-01 8:34 ` Jakub Narebski
2008-09-01 9:59 ` Karl Hasselström
2008-09-03 12:20 ` Christian Jaeger
2008-09-03 12:40 ` Eric Bowman
2008-09-03 12:46 ` Tor Arvid Lund
2008-09-03 16:49 ` Felipe Contreras
2008-09-05 13:46 ` Marc-André Lureau
2008-09-05 14:10 ` Jakub Narebski [this message]
2008-09-05 14:12 ` Petr Baudis
2008-09-05 14:45 ` Jeff King
[not found] ` <200809011305.35858.jnareb@gmail.com>
[not found] ` <20080901143718.GG10360@machine.or.cz>
2008-09-01 14:48 ` [ANNOUNCE] Git User's Survey 2008 has started Jakub Narebski
2008-09-01 14:51 ` Petr Baudis
2008-09-03 10:18 ` [ANNOUNCE] Git User's Survey 2008 Jakub Narebski
2008-09-03 10:18 ` Jakub Narebski
2008-09-03 22:47 ` Felipe Carvalho Oliveira
2008-09-04 16:39 ` Jakub Narebski
2008-09-06 9:11 ` Jakub Narebski
2008-09-08 22:58 ` Announcing " Jakub Narebski
2008-10-14 0:25 ` [ANNOUNCE] Git User's Survey 2008 has closed Jakub Narebski
2008-10-14 0:25 ` Jakub Narebski
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=m3d4jipttz.fsf_-_@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=christian@jaeger.mine.nu \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=marcandre.lureau@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.