From: Parav Pandit <parav@nvidia.com>
To: Cornelia Huck <cohuck@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: RE: [virtio-comment] delta between branch 1.4 and master
Date: Thu, 18 Jan 2024 06:49:45 +0000 [thread overview]
Message-ID: <PH0PR12MB54816E95105B692BA8386568DC712@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <87a5p4m0ig.fsf@redhat.com>
> From: Cornelia Huck <cohuck@redhat.com>
> Sent: Wednesday, January 17, 2024 9:10 PM
>
> On Wed, Jan 17 2024, Parav Pandit <parav@nvidia.com> wrote:
>
> > Hi Cornelia,
> >
> > Currently virtio spec, 1.4 branch has 6 patches which are not present in
> master.
> > And master branch has 16 patches which are not present in 1.4 branch.
> >
> > Is there a plan to sync both the trees?
> > Patches should be sent against which branch master or 1.4?
>
> This situation will be resolved by merging the 1.4 branch into master -- once
> 1.3 is finally done, which is waiting on voting and OASIS processes, which is
> waiting on the OASIS infrastructure migration... really sorry about the long
> delay, but if I had opened a vote, I'm sure that Murphy would have scheduled
> the migration right in the middle of the voting period. I will update once I
> have news.
>
> If you have any patches, please base them on the 1.4 branch.
Ok. Will use 1.4 branch. Thank you for the updates.
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/
prev parent reply other threads:[~2024-01-18 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 9:58 [virtio-comment] delta between branch 1.4 and master Parav Pandit
2024-01-17 15:40 ` Cornelia Huck
2024-01-18 6:49 ` Parav Pandit [this message]
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=PH0PR12MB54816E95105B692BA8386568DC712@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).