From: Cornelia Huck <cohuck@redhat.com>
To: "T.J. Alumbaugh" <talumbau@google.com>,
virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] trouble sending patch with git send-email
Date: Mon, 15 May 2023 17:16:56 +0200 [thread overview]
Message-ID: <877ct939qv.fsf@redhat.com> (raw)
In-Reply-To: <CABmGT5FVRj9=vrekhCOWwQnO2eOHDt8pA35hef+=BLN7fWi5=Q@mail.gmail.com>
On Mon, May 15 2023, "T.J. Alumbaugh" <talumbau@google.com> wrote:
> Hi,
>
> I'm having an issue trying to send a proposed spec change for
> discussion to this list. I'm following the instructions here:
>
> https://github.com/oasis-tcs/virtio-spec#providing-feedback
>
> which seem to be pretty standard and the typical workflow for sending
> git patches. However, my messages bounce with this error:
>
> <virtio-comment@lists.oasis-open.org>: permission denied. Command output:
> Traceback (most recent call last): File
> "/home/oasis/bin/kmlm_crosspost_issubn", line 14, in <module> import
> MySQLdb ImportError: No module named MySQLdb Sorry, only subscribers may
> post. If you are a subscriber, please forward this message to
> virtio-comment-owner@lists.oasis-open.org to get your new address included
> (#5.7.2) ERROR: postqmail-local Error #77
>
>
> I have confirmed that I am a subscriber to this list. This email
> itself will serve as an experiment to determine if the message is
> legitimate (the system believes I am not a subscriber), or if this
> error is spurious and there is some other issue with sending a patch
> with `git send-email`. In the event that this email does get through,
> any advice on how to proceed would be much appreciated! Thanks,
>
> -T.J.
Just to make sure it's not something obvious: Have you double checked
that the author in git matches the address you subscribed with? Because
this mail came through, and having the author set to a different address
without realizing it is something that happens a lot.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2023-05-15 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 14:49 [virtio-comment] trouble sending patch with git send-email T.J. Alumbaugh
2023-05-15 15:16 ` Cornelia Huck [this message]
2023-05-15 15:31 ` T.J. Alumbaugh
2023-05-15 15:46 ` Cornelia Huck
2023-05-15 15:58 ` T.J. Alumbaugh
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=877ct939qv.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=talumbau@google.com \
--cc=virtio-comment@lists.oasis-open.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox