From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hch@lst.de" <hch@lst.de>,
"jthumshirn@suse.de" <jthumshirn@suse.de>,
"snitzer@redhat.com" <snitzer@redhat.com>
Cc: "agk@redhat.com" <agk@redhat.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [PATCH v3] dm: don't allow ioctls to targets that don't map to whole devices
Date: Fri, 3 Feb 2017 21:41:16 +0000 [thread overview]
Message-ID: <1486158062.2553.12.camel@sandisk.com> (raw)
In-Reply-To: <4435311b-80e1-8764-fa12-140203e9231f@suse.de>
On Fri, 2017-02-03 at 19:17 +0100, Johannes Thumshirn wrote:
> Forgotten git add? git commit --amend without git add is such a classic
> mistake on my side as well :-/
Are you familiar with the -a option of git commit? Just run
git commit -a --amend
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hch@lst.de" <hch@lst.de>,
"jthumshirn@suse.de" <jthumshirn@suse.de>,
"snitzer@redhat.com" <snitzer@redhat.com>
Cc: "agk@redhat.com" <agk@redhat.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [PATCH v3] dm: don't allow ioctls to targets that don't map to whole devices
Date: Fri, 3 Feb 2017 21:41:16 +0000 [thread overview]
Message-ID: <1486158062.2553.12.camel@sandisk.com> (raw)
In-Reply-To: <4435311b-80e1-8764-fa12-140203e9231f@suse.de>
On Fri, 2017-02-03 at 19:17 +0100, Johannes Thumshirn wrote:
> Forgotten git add? git commit --amend without git add is such a classic=20
> mistake on my side as well :-/
Are you familiar with the -a option of git commit? Just run
git commit -a --amend
Bart.=
next prev parent reply other threads:[~2017-02-03 21:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 16:37 [PATCH v3] dm: don't allow ioctls to targets that don't map to whole devices Christoph Hellwig
2017-02-03 16:39 ` Mike Snitzer
2017-02-03 16:41 ` Christoph Hellwig
2017-02-03 18:17 ` Johannes Thumshirn
2017-02-03 18:17 ` Johannes Thumshirn
2017-02-03 21:41 ` Bart Van Assche [this message]
2017-02-03 21:41 ` Bart Van Assche
2017-02-06 7:29 ` Johannes Thumshirn
2017-02-06 7:29 ` Johannes Thumshirn
2017-02-03 16:56 ` Paolo Bonzini
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=1486158062.2553.12.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=snitzer@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 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.