From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: Using thunderbird to post/apply patches?
Date: Fri, 8 Feb 2008 12:21:24 +1300 [thread overview]
Message-ID: <46a038f90802071521n674b61c2t5e4d4c740375b951@mail.gmail.com> (raw)
Is there anyone using thunderbird/mozilla to post patches with
additional email commentary like Junio and Linus do? Are there good
tricks for this? Or otherwise a similar MUA that does things right?
The 2 workflows I am after are...
- Load up a patch created with git-format-patch into my email editor
to add some commentary before sending. Should not munge the patch
itself!
- Feed an email I am reading to git-apply-mbox so that if it's
reasonably formatted as a patch it will do the right thing and apply
it.
cheers,
m
next reply other threads:[~2008-02-07 23:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 23:21 Martin Langhoff [this message]
2008-02-07 23:34 ` Using thunderbird to post/apply patches? Johannes Schindelin
2008-02-07 23:42 ` Martin Langhoff
2008-02-08 0:12 ` Johannes Schindelin
2008-02-08 4:27 ` Martin Langhoff
2008-02-07 23:44 ` Brandon Casey
2008-02-08 4:10 ` Jay Soffian
2008-02-08 7:26 ` Junio C Hamano
2008-02-08 11:38 ` Johannes Schindelin
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=46a038f90802071521n674b61c2t5e4d4c740375b951@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).