[ovs-dev] rstp: add ability to receive VLAN-tagged BPDUs
Flavio Leitner
fbl at sysclose.org
Thu Feb 14 15:52:22 UTC 2019
On Thu, Feb 14, 2019 at 03:06:33PM +0100, Matthias May via dev wrote:
> On 14/02/2019 14:34, Flavio Leitner wrote:
> > Matthias, could you describe to where exactly you sent out the
> > patch? ovs-dev at openvswitch.org or dev at openvswitch.org or something
> > else?
> Some info:
> * git version 2.20.1
> * (Reproduced) trace of what I entered:
> ```
> maym at CHD500279:~/git/ovs$ git send-email send-email/ --no-chain-reply
> send-email/0001-rstp-add-ability-to-receive-VLAN-tagged-BPDUs.patch
> To whom should the emails be sent (if anyone)? ovs-dev at openvswitch.org
>
> Message-ID to be used as In-Reply-To for the first email (if any)?
>
> (mbox) Adding cc: Matthias May <matthias.may at neratec.com> from line 'From: Matthias May <matthias.may at neratec.com>'
> (body) Adding cc: Matthias May <matthias.may at neratec.com> from line 'Signed-off-by: Matthias May <matthias.may at neratec.com>'
>
> From: Matthias May <matthias.may at neratec.com>
> To: ovs-dev at openvswitch.org
> Cc: Matthias May <matthias.may at neratec.com>
> Subject: [PATCH] rstp: add ability to receive VLAN-tagged BPDUs
> Date: Thu, 14 Feb 2019 15:01:34 +0100
> Message-Id: <20190214140134.16754-1-matthias.may at neratec.com>
> X-Mailer: git-send-email 2.20.1
> MIME-Version: 1.0
> Content-Transfer-Encoding: 8bit
>
> The Cc list above has been expanded by additional
> addresses found in the patch commit message. By default
> send-email prompts before sending whenever this occurs.
> This behavior is controlled by the sendemail.confirm
> configuration setting.
>
> For additional information, run 'git send-email --help'.
> To retain the current behavior, but squelch this message,
> run 'git config --global sendemail.confirm auto'.
>
> Send this email? ([y]es|[n]o|[e]dit|[q]uit|[a]ll): y
>
> ```
>
> This obviously has a different Message-Id then the mail sent before.
Do you mind to send the same patch to dev at openvswitch.org to see if
that happens again? I don't know how the list is configured but so
far it only happened with ovs-dev@ and not with dev at .
Thanks,
fbl
More information about the dev
mailing list