From: "Michael S. Tsirkin" <mst@redhat.com>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: "virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: vhost stable branch
Date: Fri, 2 Jun 2023 08:22:09 -0400 [thread overview]
Message-ID: <20230602082154-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <b8172a255a7a48524c3454676e11d2e8e1386634.camel@nvidia.com>
On Tue, May 30, 2023 at 10:19:18AM +0000, Dragos Tatulea wrote:
> On Tue, 2023-05-23 at 07:45 -0400, Michael S. Tsirkin wrote:
> > On Tue, May 23, 2023 at 08:38:47AM +0000, Dragos Tatulea wrote:
> > > On Tue, 2023-05-23 at 04:18 -0400, Michael S. Tsirkin wrote:
> > > > On Tue, May 23, 2023 at 07:16:58AM +0000, Dragos Tatulea wrote:
> > > > > Hi,
> > > > >
> > > > > I am looking for the stable branch for vdpa fixes in the vhost tree [1].
> > > > > There
> > > > > are 3 branches that seem identical: linux-next, test and vhost. linux-
> > > > > next
> > > > > seems
> > > > > to be -next branch. Which one would be the stable branch?
> > > > >
> > > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
> > > > >
> > > > > Thanks,
> > > > > Dragos
> > > >
> > > > I don't publish one until I am ready to send patches to Linus.
> > > > Which should be today or tomorrow.
> > > >
> > > Understood. Is it the same with patches for -next? Are they published only
> > > once
> > > the patches are sent to Linus?
> > >
> > > Thanks,
> > > Dragos
> > >
> >
> > A bit different. I start worrying about next when I'm done with stable.
> > Also my next branch rebases frequently, I also drop and squash patches,
> > rewrite commit log etc.
> >
> Is the linux-next branch in the referenced tree [1] the next branch or is it
> hosted somewhere else? I am asking because I haven't seen any rebases in the
> last 4+ weeks in the referenced location. I want to make sure that I'm looking
> in the right location.
>
> Thanks,
> Dragos
>
pushed to next now.
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-06-02 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 7:16 vhost stable branch Dragos Tatulea via Virtualization
2023-05-23 8:18 ` Michael S. Tsirkin
2023-05-23 8:38 ` Dragos Tatulea via Virtualization
2023-05-23 11:45 ` Michael S. Tsirkin
2023-05-30 10:19 ` Dragos Tatulea via Virtualization
2023-06-02 12:22 ` Michael S. Tsirkin [this message]
2023-06-02 16:05 ` Dragos Tatulea via Virtualization
2023-05-23 8:28 ` Michael S. Tsirkin
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=20230602082154-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dtatulea@nvidia.com \
--cc=virtualization@lists.linux-foundation.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.