All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Laplante" <chris.laplante@agilent.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH v3 00/10] optparse => argparse
Date: Wed, 18 Nov 2020 17:07:09 +0000	[thread overview]
Message-ID: <SN1PR12MB24809AE9781F70F9F4ADBCCD8BE10@SN1PR12MB2480.namprd12.prod.outlook.com> (raw)
In-Reply-To: <710819fcc1b29838ea7d2f2b332fdd44495219c7.camel@linuxfoundation.org>

> > Can you please tell me specifically how the patches I'm sending are
> > getting mangled? I'm having trouble finding information online about
> > how I may fix this.
> >
> > I also can't find an automated way of adding 'From: ' lines to the
> > emails produced by git send-email.
> 
> groups.io (where the list is hosted) is rewriting your email address since your
> domain does not allow it to send out messages 'pretending'
> to be <something>@agilent.com. This is a general problem mailing lists have
> with increased spam protections that are now in place. The rewritten version
> is "Chris Laplante via lists.openembedded.org
> <chris.laplante=agilent.com@lists.openembedded.org>" which works as we
> allow groups.io to sent from lists.openembedded.org.
> 
> If you can influence the DNS/SPF for agilent.com, you can probably improve
> things otherwise we're into workaround territory on one end or the other.
> 
> I can handle it worst case, I probably just need to increase the automation of
> my patch handling and some brute force sed hackery...

Unfortunately I doubt I can do anything about the DNS/SPF:(

I'd rather avoid you needing to make changes to your scripting just to deal with my patches, so I'll make sure to set the 'From: ' header. I'm going to submit a patch soon as a kind of test to see if it works (though it is an actual patch for an issue I found, separate from all the argparse stuff).

N.B.: I really wish git had a hook that runs at 'send-email' time. As I understand it, that would be the correct place to automatically prefix the message body with the 'From: ' header. I tried using 'prepare-commit-msg' to prefix the entire commit message with 'From: ' but that dirties the log and breaks 'git log --oneline'. Maybe I'm missing something but I just don't see a way to do this automatically without writing a wrapper script around send-email, which I'll probably end up doing.

Thanks,
Chris

  reply	other threads:[~2020-11-18 17:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-08 22:10 [PATCH v3 00/10] optparse => argparse Chris Laplante
2020-11-08 22:10 ` [PATCH v3 01/10] cookerdata: tweak to avoid mutable default argument Chris Laplante
2020-11-08 22:10 ` [PATCH v3 02/10] tests/arg_parser: add stub for testing arg parsing Chris Laplante
2020-11-08 22:10 ` [PATCH v3 03/10] tests/arg_parser: add test for 'bitbake -S none world' Chris Laplante
2020-11-08 22:10 ` [PATCH v3 04/10] main: migrate from optparse to argparse Chris Laplante
2020-11-08 22:10 ` [PATCH v3 05/10] main: group --help options to make them easier to read Chris Laplante
2020-11-08 22:10 ` [PATCH v3 06/10] main: rename list_extension_modules => load_extension_modules to clarify its function Chris Laplante
2020-11-08 22:10 ` [PATCH v3 07/10] tests/arg_parser: add test for lazy loading of bb.ui modules Chris Laplante
2020-11-08 22:10 ` [PATCH v3 08/10] main: fix parsing of intermixed arguments Chris Laplante
2020-11-08 22:10 ` [PATCH v3 09/10] tinfoil: use knotty module itself as default 'ui' arg to keep up with changes in setup_bitbake Chris Laplante
2020-11-08 22:10 ` [PATCH v3 10/10] tests/arg_parser: add test for default TinfoilConfigParameters 'ui' Chris Laplante
2020-11-10 21:33 ` [bitbake-devel] [PATCH v3 00/10] optparse => argparse Richard Purdie
2020-11-10 21:36   ` Chris Laplante
2020-11-10 21:38 ` Richard Purdie
2020-11-10 21:40   ` Chris Laplante
2020-11-18 16:37   ` Chris Laplante
2020-11-18 16:44     ` Richard Purdie
2020-11-18 17:07       ` Chris Laplante [this message]
2020-11-18 17:24         ` Richard Purdie
2020-11-18 21:01           ` Chris Laplante
2020-11-20 11:17             ` Richard Purdie
     [not found]       ` <1648A9226B93C86E.28066@lists.openembedded.org>
2020-11-18 17:08         ` Chris Laplante

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=SN1PR12MB24809AE9781F70F9F4ADBCCD8BE10@SN1PR12MB2480.namprd12.prod.outlook.com \
    --to=chris.laplante@agilent.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 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.