From: Cornelia Huck <cohuck@redhat.com>
To: "T.J. Alumbaugh" <talumbau@google.com>
Cc: virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] trouble sending patch with git send-email
Date: Mon, 15 May 2023 17:46:25 +0200 [thread overview]
Message-ID: <87y1lp1tta.fsf@redhat.com> (raw)
In-Reply-To: <CABmGT5EW_D7DWKM5WAGruyvyDiNv8R8_hGZXUvDc3itUZLeaQw@mail.gmail.com>
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/
next prev parent reply other threads:[~2023-05-15 15:46 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
2023-05-15 15:31 ` T.J. Alumbaugh
2023-05-15 15:46 ` Cornelia Huck [this message]
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=87y1lp1tta.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 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.