[Pkg-xen-devel] irt: [PATCH 00/12] Bunch of patches for cross-compilatio + RP4

[Elliott Mitchell]

On Mon, Jul 20, 2020 at 02:30:30PM +0200, Hans van Kranenburg wrote:
> Hi,
> 
> On 7/19/20 8:01 AM, Elliott Mitchell wrote:
> > Taking the output of `git format-patch` and piping it to a mailer is a
> > potentially hazardous art.  If you don't /quite/ get things right you can
> > end up faking the sender of a message.
> > 
> > Please note the patches 9-11 were sent by me, though Julien Grall is the
> > original author.
> 
> Hah. :)
> 
> The git send-email program can do the actual emailing, and then it sets
> all mail dates to the current time (so that the mails end up 00-12 if
> you get them instead of in order of original commit date, which is now
> 9,10-11,5,6,2,etc). It will also put you as sender, and then add the
> "From: Foo <foo at bar>" line as first in the email, which causes it to be
> put back as commit author when using git am.
> 
> e.g.
> 
>     git send-email --suppress-cc=all --dry-run 00*
> 
> You want the suppress-cc because otherwise you'll be causing mails to be
> sent to Julian and everyone who has Reviewed-by etc lines in the
> original commits.
> 
> Dry-run shows the smtp header stuff to verify.
> 
> Feel free to re-send.

Thing is my setup is git repositories on one system, mail gets sent by
another.  This comes near what I want with `git format-patch` and is
quite different from the approach `git send-email` is designed for.

Since I can see from the public list archives everything went through,
is there an actual need to resend?


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sigmsg at m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445