Thanks for the instructions. I will do it. Jay On Fri, Mar 7, 2025 at 5:05 PM Mike Pattrick <m...@redhat.com> wrote:
> On Fri, Mar 7, 2025 at 4:44 PM Jay Ding <jay.d...@broadcom.com> wrote: > > > > okay I will do it. > > > > Is this the right way to reply to the list and put a new patch in? > > > > git send-email your-patch.patch --to d...@openvswitch.org --in-reply-to < > 87bkcrk483....@redhat.com> > > > > Sorry, it is my first time to submit the changes. > > No worries! You don't actually need to set in-reply-to. > > Typically for a version 2 patch I'll do something like: > > $ git format-patch -v2 -1 > $ python utilities/checkpatch.py [filename] > $ git send-email --to ovs-dev@openvswitch.org [filename] > > Cheers, > M > > > > > Jay > > On Fri, Mar 7, 2025 at 10:54 AM Kevin Traynor <ktray...@redhat.com> > wrote: > >> > >> On 06/03/2025 18:11, Jay Ding wrote: > >> > On Thu, Mar 6, 2025 at 9:55 AM Kevin Traynor <ktray...@redhat.com> > wrote: > >> > > >> >> On 04/03/2025 16:51, Jay Ding wrote: > >> >>> I actually send it through "git send-email". > >> >>> > >> >>> Thanks, > >> >>> Jay > >> >>> > >> >> > >> >> Hi Jay. Thanks for the patch. I didn't see it on the mailing list. It > >> >> should be sent with something like, > >> >> 'git send-email <patchname>.patch --to=d...@openvswitch.org' > >> >> > >> >> Might be easiest to test with your own email as the --to to check > it's > >> >> sending ok. > >> >> > >> >> As it's just a one line patch, I updated the subject and re-posted > for > >> >> you to the mailing list here: > >> >> > https://mail.openvswitch.org/pipermail/ovs-dev/2025-March/421886.html > >> >> > >> >> Kevin. > >> >> > >> >> p.s. The mailing list convention is to not top-post in emails, but to > >> >> reply inline! > >> >> > >> > >> > Hi Kevin, > >> > > >> > Many thanks for helping resubmit it. I did see the patch in my own > >> > email when sending to the mail list because I was cc-ed myself. > >> > > >> > Thanks, > >> > Jay > >> > > >> > >> ^^^^ the reply goes here after the last comment so others can follow it > >> like a conversation :-) > >> > >> Hi Jay, I see Mike has posted a comment on your patch, perhaps you can > >> reply ? > >> > >> https://mail.openvswitch.org/pipermail/ovs-dev/2025-March/421906.html > >> > >> thanks, > >> Kevin. > >> > > > > This electronic communication and the information and any files > transmitted with it, or attached to it, are confidential and are intended > solely for the use of the individual or entity to whom it is addressed and > may contain information that is confidential, legally privileged, protected > by privacy laws, or otherwise restricted from disclosure to anyone else. If > you are not the intended recipient or the person responsible for delivering > the e-mail to the intended recipient, you are hereby notified that any use, > copying, distributing, dissemination, forwarding, printing, or copying of > this e-mail is strictly prohibited. If you received this e-mail in error, > please return the e-mail to the sender, delete it from your computer, and > destroy any printed copy of it. > > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
_______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
