On Aug 26 07:28, Keith Busch wrote:
> On Tue, Aug 25, 2020 at 10:43:23PM +0100, Peter Maydell wrote:
> > On Tue, 25 Aug 2020 at 21:12, Keith Busch wrote:
> > >
> > > On Sun, Aug 23, 2020 at 02:56:12PM +0100, Peter Maydell wrote:
> > > > Hi; it looks like this isn't a gpg-signed tag?
> > > >
> > >
On Tue, Aug 25, 2020 at 10:43:23PM +0100, Peter Maydell wrote:
> On Tue, 25 Aug 2020 at 21:12, Keith Busch wrote:
> >
> > On Sun, Aug 23, 2020 at 02:56:12PM +0100, Peter Maydell wrote:
> > > Hi; it looks like this isn't a gpg-signed tag?
> > >
> > > error: remotes/nvme/nvme-next: cannot verify a n
On Tue, 25 Aug 2020 at 21:12, Keith Busch wrote:
>
> On Sun, Aug 23, 2020 at 02:56:12PM +0100, Peter Maydell wrote:
> > Hi; it looks like this isn't a gpg-signed tag?
> >
> > error: remotes/nvme/nvme-next: cannot verify a non-tag object of type
> > commit.
>
> Oops, sorry I forgot about that part
On Sun, Aug 23, 2020 at 02:56:12PM +0100, Peter Maydell wrote:
> On Wed, 19 Aug 2020 at 20:23, Keith Busch wrote:
> >
> > We're trying our first nvme pull request from a dedicated development
> > tree containing various fixes, cleanups, spec compliance, and welcoming
> > Klaus Jensen to maintainin
On Wed, 19 Aug 2020 at 20:23, Keith Busch wrote:
>
> We're trying our first nvme pull request from a dedicated development
> tree containing various fixes, cleanups, spec compliance, and welcoming
> Klaus Jensen to maintaining the emulated nvme device development.
>
> The following changes since c
We're trying our first nvme pull request from a dedicated development
tree containing various fixes, cleanups, spec compliance, and welcoming
Klaus Jensen to maintaining the emulated nvme device development.
The following changes since commit d0ed6a69d399ae193959225cdeaa9382746c91cc:
Update ver
