DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: 王颢 <howard_wang@realsil.com.cn>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Inquiry Regarding Sending Patches to DPDK
Date: Mon, 12 Aug 2024 07:55:39 -0700	[thread overview]
Message-ID: <20240812075539.20a77c1c@hermes.local> (raw)
In-Reply-To: <992435800910458fbf93a7c59ff454fc@realsil.com.cn>

On Mon, 12 Aug 2024 07:52:39 +0000
王颢 <howard_wang@realsil.com.cn> wrote:

> Dear all,
> 
> I hope this message finds you well.
> 
> I would like to seek your advice on an issue I've encountered. Our company has recently enabled two-factor authentication (2FA) for our email accounts. The IT department has suggested that I abandon using the "git send-email" method, as configured through git config, to send patches to DPDK. Instead, they have recommended using "Exchange anonymous send mail." However, I believe this approach might not be feasible.
> 
> I wanted to confirm this with you and see if you could provide any guidance on the matter. I look forward to your response.
> 
> Thank you very much for your time and assistance.
> 
> Best regards,
> Howard Wang

There are two issues here:
Using git send-email is not required. You can generate patch files and put them in
your email.
BUT Microsoft Exchange does not preserve text formatting in messages. Any patches sent
that way are usually corrupted.

At Microsoft, we ended up using a special server (not Exchange) to send Linux and DPDK
patches. Or using non-corporate accounts.

  reply	other threads:[~2024-08-12 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12  7:52 王颢
2024-08-12 14:55 ` Stephen Hemminger [this message]
2024-08-14  9:51   ` 答复: " 王颢
2024-08-14 10:14     ` Morten Brørup
2024-08-15  7:55       ` 答复: " 王颢

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=20240812075539.20a77c1c@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=howard_wang@realsil.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).