All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Schoenebeck via <qemu-devel@nongnu.org>
To: qemu-devel@nongnu.org
Cc: berrange@redhat.com, stefanha@gmail.com,
	Christian Schoenebeck <qemu_oss@crudebyte.com>,
	Greg Kurz <groug@kaod.org>,
	dgilbert@redhat.com, antonios.motakis@huawei.com,
	Ian Kelling <iank@fsf.org>
Subject: Re: [Qemu-devel] [PATCH v6 0/4] 9p: Fix file ID collisions
Date: Mon, 23 Sep 2019 13:27:37 +0200	[thread overview]
Message-ID: <5814161.pL1kAXq1mB@silver> (raw)
In-Reply-To: <20190905145931.3748d5f2@bahia.lan>

On Donnerstag, 5. September 2019 14:59:31 CEST Greg Kurz wrote:
> On Thu, 05 Sep 2019 14:25:13 +0200
> 
> Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
> > On Mittwoch, 4. September 2019 15:02:30 CEST Christian Schoenebeck wrote:
> > > > > Well, mailman is handling this correctly. It replaces the "From:"
> > > > > field
> > > > > with a placeholder and instead adds my actual email address as
> > > > > "Reply-To:" field. That's the common way to handle this on mailing
> > > > > lists,
> > > > > as also mentioned here:
> > > > > https://en.wikipedia.org/wiki/DMARC#From:_rewriting
> > > > > 
> > > > > So IMO patchew should automatically use the value of "Reply-To:" in
> > > > > that
> > > > > case as author of patches instead.
> > > > > 
> > > > > Reducing security cannot be the solution.
> > > > 
> > > > No, there's no need to reduce security.  Just change your local git
> > > > configuration to produce a 'From:' line in the commit body..
> > > 
> > > Got it. :)
> > > 
> > > > >> How are you sending patches ? With git send-email ? If so, maybe
> > > > >> you
> > > > >> can
> > > > >> pass something like --from='"Christian Schoenebeck"
> > > > >> <qemu_oss@crudebyte.com>'. Since this is a different string, git
> > > > >> will
> > > > >> assume you're sending someone else's patch : it will automatically
> > > > >> add
> > > > >> an
> > > > >> extra From: made out of the commit Author as recorded in the git
> > > > >> tree.
> > > > 
> > > > I think it is probably as simple as a 'git config' command to tell git
> > > > to always put a 'From:' in the body of self-authored patches when
> > > > using
> > > > git format-patch; however, as I don't suffer from munged emails, I
> > > > haven't actually tested what that setting would be.
> > 
> > Well, I tried that Eric. The expected solution would be enabling this git
> > setting:
> > 
> > git config [--global] format.from true
> > https://git-scm.com/docs/git-config#Documentation/git-config.txt-formatfro
> > m
> > 
> > But as you can already read from the manual, the overall behaviour of git
> > regarding a separate "From:" line in the email body was intended solely
> > for
> > the use case sender != author. So in practice (at least in my git version)
> > git always makes a raw string comparison between sender (name and email)
> > string and author string and only adds the separate From: line to the
> > body if they differ.
> > 
> > Hence also "git format-patch --from=" only works here if you use a
> > different author string (name and email) there, otherwise on a perfect
> > string match it is simply ignored and you end up with only one "From:" in
> > the email header.
> > 
> > So eventually I added one extra character in my name for now and removed
> > it
> > manually in the dumped emails subsequently (see today's
> > "[PATCH v7 0/3] 9p: Fix file ID collisions").
> 
> Hence my proposal in some other mail to pass a different string to
> git send-email, but I guess this also works for git format-patch.
> 
> eg, adding double quotes around your "firstname name"
> 
>  --from='"Christian Schoenebeck" <qemu_oss@crudebyte.com>'

Yeah, I will use that for now, since it just works^TM (I tested it).

Because for some reason my emails are still mangled on this list. Probably I 
still have to drop more header fields from dkim's "h=..." setting. We'll see.





  reply	other threads:[~2019-09-23 11:28 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 19:53 [Qemu-devel] [PATCH v6 0/4] 9p: Fix file ID collisions Christian Schoenebeck via Qemu-devel
2019-08-22 19:28 ` [Qemu-devel] [PATCH v6 1/4] 9p: Treat multiple devices on one export as an error Christian Schoenebeck via Qemu-devel
2019-08-29 16:27   ` Greg Kurz
2019-09-01 17:38     ` Christian Schoenebeck via Qemu-devel
2019-08-22 19:33 ` [Qemu-devel] [PATCH v6 2/4] 9p: Added virtfs option 'multidevs=remap|forbid|warn' Christian Schoenebeck via Qemu-devel
2019-08-29 16:55   ` Greg Kurz
2019-09-01 18:40     ` Christian Schoenebeck via Qemu-devel
2019-09-02 10:16       ` Greg Kurz
2019-09-02 21:07         ` Christian Schoenebeck via Qemu-devel
2019-08-30 12:22   ` Greg Kurz
2019-09-01 18:56     ` Christian Schoenebeck via Qemu-devel
2019-09-02 11:49       ` Greg Kurz
2019-09-02 21:25         ` Christian Schoenebeck via Qemu-devel
2019-08-22 19:44 ` [Qemu-devel] [PATCH v6 3/4] 9p: stat_to_qid: implement slow path Christian Schoenebeck via Qemu-devel
2019-08-22 19:49 ` [Qemu-devel] [PATCH v6 4/4] 9p: Use variable length suffixes for inode remapping Christian Schoenebeck via Qemu-devel
2019-08-22 22:18 ` [Qemu-devel] [PATCH v6 0/4] 9p: Fix file ID collisions no-reply
2019-08-29 17:02   ` Greg Kurz
2019-09-01 19:28     ` Christian Schoenebeck via Qemu-devel
2019-09-02 15:34       ` Greg Kurz
2019-09-02 22:29         ` Christian Schoenebeck via Qemu-devel
2019-09-03 19:11           ` [Qemu-devel] DMARC/DKIM and qemu-devel list settings Ian Kelling
2019-09-04  8:13             ` Daniel P. Berrangé
2019-09-04 14:19               ` Ian Kelling
2019-09-04 14:30             ` Peter Maydell
2019-09-09 11:47               ` Markus Armbruster
2019-09-10  7:23               ` Stefan Hajnoczi
2019-09-03 19:38           ` [Qemu-devel] [PATCH v6 0/4] 9p: Fix file ID collisions Eric Blake
2019-09-04 13:02             ` Christian Schoenebeck via Qemu-devel
2019-09-05 12:25               ` Christian Schoenebeck via Qemu-devel
2019-09-05 12:59                 ` Greg Kurz
2019-09-23 11:27                   ` Christian Schoenebeck via [this message]
2019-09-09 14:05                 ` Eric Blake
2019-09-09 14:05                   ` Eric Blake
2019-09-09 14:25                   ` Jeff King
2019-09-09 14:25                     ` Jeff King
2019-09-23 11:19                     ` Christian Schoenebeck
2019-09-23 11:19                       ` Christian Schoenebeck via
2019-09-23 22:24                       ` Jeff King
2019-09-23 22:24                         ` Jeff King
2019-09-24  9:03                         ` git format.from (was: 9p: Fix file ID collisions) Christian Schoenebeck
2019-09-24  9:03                           ` Christian Schoenebeck via
2019-09-24 21:36                           ` Jeff King
2019-09-24 21:36                             ` Jeff King
2019-09-09 18:41                   ` [Qemu-devel] [PATCH v6 0/4] 9p: Fix file ID collisions Junio C Hamano
2019-09-09 18:41                     ` Junio C Hamano

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=5814161.pL1kAXq1mB@silver \
    --to=qemu-devel@nongnu.org \
    --cc=antonios.motakis@huawei.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=groug@kaod.org \
    --cc=iank@fsf.org \
    --cc=qemu_oss@crudebyte.com \
    --cc=stefanha@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.