From: Henning Schild <henning.schild@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] dpkg class sbuild allows extra arguments by vars
Date: Wed, 4 Jan 2023 08:53:58 +0100 [thread overview]
Message-ID: <20230104085358.2f416b68@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CAJGKYO7jnapMShpKJ5ws_k3wZhyZYNVXbHChrngP7tywWbxPnA@mail.gmail.com>
Am Tue, 3 Jan 2023 22:39:55 +0100
schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
> On Tue, 3 Jan 2023 at 21:26, Henning Schild
> <henning.schild@siemens.com> wrote:
> >
> > Again can you please send you patches in a way that they can
> > actually be reviewed in a mail based workflow.
>
> I send the patches with git-send but they went in moderation and
> usually remain there.
> Tomorrow, I will search for another open SMTP server hoping that the
> m-list will accept it but I am desperate to find one that suits the
> stringent anti-spam rules of google.
Maybe we start with your problem here and help you use the SMTP servers
from google. My guess is that you might be struggling with 2FA. And
doing an internet search on how to use plain SMTP on gmail might also
give you the solution.
Using any other SMTP server you will likely get problems with SPF,
DKIM, DMARC forcing you to send emails "From" the domain of that other
server. In which case git-send-email would put a secondary "From" into
the commit message so that git-am on the other side will get the real
author email.
But best try to use googles SMTP servers, that is for sure possible and
not too hard once you found the solution.
Henning
> > You have conducted reviews yourself already so you should know how
> > things should work.
>
> ...and everytime, I send a patch I always let people here remember
> about the problem.
> For compensation, I started to add this link
>
> > >
> > > https://github.com/ilbers/isar/commit/7e72921747aedf588af492be95fb0b91ad70f455
> > >
> >
>
> Best regards, R-
next prev parent reply other threads:[~2023-01-04 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 19:58 Roberto A. Foglietta
2023-01-03 20:26 ` Henning Schild
2023-01-03 21:39 ` Roberto A. Foglietta
2023-01-04 7:53 ` Henning Schild [this message]
2023-01-05 17:43 ` Roberto A. Foglietta
2023-01-05 18:31 ` Henning Schild
2023-01-05 18:43 ` Roberto A. Foglietta
2023-01-25 12:27 ` Uladzimir Bely
2023-01-25 16:12 ` Roberto A. Foglietta
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=20230104085358.2f416b68@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox