qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Klaus Jensen <its@irrelevant.dk>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Qemu-block <qemu-block@nongnu.org>,
	Klaus Jensen <k.jensen@samsung.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Max Reitz <mreitz@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Keith Busch <kbusch@kernel.org>, Fam Zheng <fam@euphon.net>
Subject: Re: [PULL 00/11] emulated nvme updates and fixes
Date: Mon, 22 Mar 2021 20:27:42 +0100	[thread overview]
Message-ID: <YFjvrqLZTPW+EVZP@apples.localdomain> (raw)
In-Reply-To: <YFNDfeymKdQN/XT2@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]

On Mar 18 12:11, Daniel P. Berrangé wrote:
> On Thu, Mar 18, 2021 at 01:01:58PM +0100, Klaus Jensen wrote:
> > On Mar 18 11:28, Peter Maydell wrote:
> > > On Thu, 18 Mar 2021 at 11:27, Klaus Jensen <its@irrelevant.dk> wrote:
> > > >
> > > > On Mar 18 11:26, Peter Maydell wrote:
> > > > > On Tue, 16 Mar 2021 at 21:47, Klaus Jensen <its@irrelevant.dk> wrote:
> > > > > Hi. This tag includes a submodule update which is not mentioned
> > > > > in the cover letter or listed in the cover letter diffstat:
> > > > >
> > > > >  roms/opensbi           |    2 +-
> > > > >
> > > > > so I suspect it was inadvertent. Please fix up and resend.
> > > > >
> > > >
> > > > Oh crap. Sorry!
> > > 
> > > No worries -- git makes this a very easy mistake to make when
> > > doing rebases. That's why I have a check for it in my 'apply
> > > a pull request' scripts :-)
> > > 
> > 
> > Out of curiosity, are there any obvious safe guards I can implement
> > myself to stop this from happening?
> 
> AFAICT, latest versions of git no longer add a submodule when doing
> "git add -u". You have to explicitly specify the submodule path
> to stage it. So this prevent exactly this kind of accident.
> 

Never said thanks for that tip, so Thanks! :)

git commit -a is a pretty bad habbit and it's too bad it can't easily be
disallowed in the config file ;)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2021-03-22 19:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 21:47 [PULL 00/11] emulated nvme updates and fixes Klaus Jensen
2021-03-16 21:47 ` [PULL 01/11] hw/block/nvme: fix potential overflow Klaus Jensen
2021-03-16 21:47 ` [PULL 02/11] hw/block/nvme: assert namespaces array indices Klaus Jensen
2021-03-16 21:47 ` [PULL 03/11] hw/block/nvme: fix zone management receive reporting too many zones Klaus Jensen
2021-03-16 21:47 ` [PULL 04/11] hw/block/nvme: add metadata support Klaus Jensen
2021-03-16 21:47 ` [PULL 05/11] hw/block/nvme: end-to-end data protection Klaus Jensen
2021-03-16 21:47 ` [PULL 06/11] hw/block/nvme: add verify command Klaus Jensen
2021-03-16 21:47 ` [PULL 07/11] hw/block/nvme: add non-mdts command size limit for verify Klaus Jensen
2021-03-16 21:47 ` [PULL 08/11] hw/block/nvme: support multiple lba formats Klaus Jensen
2021-03-16 21:47 ` [PULL 09/11] hw/block/nvme: prefer runtime helpers instead of device parameters Klaus Jensen
2021-03-16 21:47 ` [PULL 10/11] hw/block/nvme: pull lba format initialization Klaus Jensen
2021-03-16 21:47 ` [PULL 11/11] hw/block/nvme: add support for the format nvm command Klaus Jensen
2021-03-18 11:26 ` [PULL 00/11] emulated nvme updates and fixes Peter Maydell
2021-03-18 11:27   ` Klaus Jensen
2021-03-18 11:28     ` Peter Maydell
2021-03-18 12:01       ` Klaus Jensen
2021-03-18 12:11         ` Daniel P. Berrangé
2021-03-22 19:27           ` Klaus Jensen [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=YFjvrqLZTPW+EVZP@apples.localdomain \
    --to=its@irrelevant.dk \
    --cc=berrange@redhat.com \
    --cc=fam@euphon.net \
    --cc=k.jensen@samsung.com \
    --cc=kbusch@kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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 NNTP newsgroup(s).