From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: I need a `git format-patch --attach-complete' for RT
Date: Wed, 21 Apr 2010 12:22:24 +0000 [thread overview]
Message-ID: <q2j51dd1af81004210522ze6062110j2033788601e17ce8@mail.gmail.com> (raw)
I'm working with a system that doesn't play nice with git-format-patch
/ git-send-email. When you send mail to RT (e.g. http://rt.perl.org/)
it'll always munge the original E-Mail, so inline patches won't
work. Here's an example of this gone wrong:
commit f9bcfeacc119e37fd70816a2cb4678fded53e8d1
Author: Ãvar Arnfjörð Bjarmason) (via RT <perlbug-followup@perl.org>
Date: Tue Apr 20 10:58:37 2010 -0700
GitHub's mirror is now at mirrors/perl, not github/perl
# New Ticket Created by (Ævar Arnfjörð Bjarmason)
# Please include the string: [perl #74532]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=74532 >
From: Ævar Arnfjörð Bjarmason <avar@cpan.org>
The workaround is to:
git format-patch --stdout origin.. > my-patches.patch
*open your mail client*
*attach patch as attachment*
*send to RT*
It would be nicer if I could instead:
git format-patch --attach-complete origin..
git send-email *.patch
The --attach option doesn't work with RT because `git am' will take
the commit message from the Subject/body of the message. RT messes
with that.
Is there some existing workaround for this that I've missed?
next reply other threads:[~2010-04-21 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 12:22 Ævar Arnfjörð Bjarmason [this message]
2010-04-29 7:25 ` I need a `git format-patch --attach-complete' for RT Paolo Bonzini
2010-04-29 10:16 ` Ævar Arnfjörð Bjarmason
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=q2j51dd1af81004210522ze6062110j2033788601e17ce8@mail.gmail.com \
--to=avarab@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).