git/list[1] front-page[2] threads[3] people[4] search[5] about
 

I need a `git format-patch --attach-complete' for RT

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Apr 21, 2010, 12:22 UTC
Message-ID
<q2j51dd1af81004210522ze6062110j2033788601e17ce8@mail.gmail.com>

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: Paolo Bonzini
Message 1 of 3 in “I need a `git format-patch --attach-complete' for RT”
  1. Ævar Arnfjörð BjarmasonApr 21, 2010
  2. Paolo BonziniApr 29, 2010
  3. Ævar Arnfjörð BjarmasonApr 29, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.