* [virtio-comment] trouble sending patch with git send-email
@ 2023-05-15 14:49 T.J. Alumbaugh
2023-05-15 15:16 ` Cornelia Huck
0 siblings, 1 reply; 5+ messages in thread
From: T.J. Alumbaugh @ 2023-05-15 14:49 UTC (permalink / raw)
To: virtio-comment
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.
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/
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [virtio-comment] trouble sending patch with git send-email
2023-05-15 14:49 [virtio-comment] trouble sending patch with git send-email T.J. Alumbaugh
@ 2023-05-15 15:16 ` Cornelia Huck
2023-05-15 15:31 ` T.J. Alumbaugh
0 siblings, 1 reply; 5+ messages in thread
From: Cornelia Huck @ 2023-05-15 15:16 UTC (permalink / raw)
To: T.J. Alumbaugh, virtio-comment
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/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [virtio-comment] trouble sending patch with git send-email
2023-05-15 15:16 ` Cornelia Huck
@ 2023-05-15 15:31 ` T.J. Alumbaugh
2023-05-15 15:46 ` Cornelia Huck
0 siblings, 1 reply; 5+ messages in thread
From: T.J. Alumbaugh @ 2023-05-15 15:31 UTC (permalink / raw)
To: Cornelia Huck; +Cc: virtio-comment
[-- Attachment #1: Type: text/plain, Size: 3422 bytes --]
On Mon, May 15, 2023 at 9:17 AM Cornelia Huck <cohuck@redhat.com> wrote:
>
>
> 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.
>
Thanks for the suggestion. I confirmed that the Author for the git commit
matches this email address:
Author: T.J. Alumbaugh <talumbau@google.com>
I also generated a cover letter for the patch, since it seems reasonable to
include a significant "Motivation" section for a spec addition. That step
is actually not in the guidance, but other than that, it's a pretty
"vanilla" patch as far as I can tell. Is it undesirable to send cover
letters for patches?
-T.J.
On Mon, May 15, 2023 at 9:17 AM Cornelia Huck <cohuck@redhat.com> wrote:
> 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/
>
>
[-- Attachment #2: Type: text/html, Size: 5231 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [virtio-comment] trouble sending patch with git send-email
2023-05-15 15:31 ` T.J. Alumbaugh
@ 2023-05-15 15:46 ` Cornelia Huck
2023-05-15 15:58 ` T.J. Alumbaugh
0 siblings, 1 reply; 5+ messages in thread
From: Cornelia Huck @ 2023-05-15 15:46 UTC (permalink / raw)
To: T.J. Alumbaugh; +Cc: virtio-comment
On Mon, May 15 2023, "T.J. Alumbaugh" <talumbau@google.com> wrote:
> On Mon, May 15, 2023 at 9:17 AM Cornelia Huck <cohuck@redhat.com> wrote:
>>
>>
>> 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.
>>
>
> Thanks for the suggestion. I confirmed that the Author for the git commit
> matches this email address:
>
> Author: T.J. Alumbaugh <talumbau@google.com>
>
> I also generated a cover letter for the patch, since it seems reasonable to
> include a significant "Motivation" section for a spec addition. That step
> is actually not in the guidance, but other than that, it's a pretty
> "vanilla" patch as far as I can tell. Is it undesirable to send cover
> letters for patches?
Presence of a cover letter or not should not make any difference whether
the mailing list accepts your post (I'd probably add a cover letter only
if the motivation section is too extensive for living in the git
repository in the end; if it should be included, there is nothing wrong
with a longer patch desription.)
Maybe you can try to cc: me on your submission? Then I can see where
things might have gone wrong. (Via the "--cc" option.)
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/
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-05-15 15:58 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-05-15 14:49 [virtio-comment] trouble sending patch with git send-email T.J. Alumbaugh
2023-05-15 15:16 ` Cornelia Huck
2023-05-15 15:31 ` T.J. Alumbaugh
2023-05-15 15:46 ` Cornelia Huck
2023-05-15 15:58 ` T.J. Alumbaugh
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.