From: Karel Zak <kzak@redhat.com>
To: Davidlohr Bueso <dave@gnu.org>
Cc: "Voelker, Bernhard" <bernhard.voelker@siemens-enterprise.com>,
util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH v3 3/4] lslocks: new command
Date: Wed, 29 Feb 2012 14:36:19 +0100 [thread overview]
Message-ID: <20120229133619.GA8471@x2.net.home> (raw)
In-Reply-To: <1330363740.2540.8.camel@offbook>
On Mon, Feb 27, 2012 at 06:29:00PM +0100, Davidlohr Bueso wrote:
> misc-utils/lslocks.c | 546 ++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 546 insertions(+), 0 deletions(-)
> create mode 100644 misc-utils/lslocks.c
Applied with some minor changes, thanks!
Please, next time keep your patches consistent -- for example if you
add lslock.c to Makefile.am then the file lslock.c should be already
exist in the tree.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2012-02-29 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 15:41 [PATCH v3 3/4] lslocks: new command Davidlohr Bueso
2012-02-27 17:16 ` Voelker, Bernhard
2012-02-27 17:19 ` Davidlohr Bueso
2012-02-27 17:29 ` Davidlohr Bueso
2012-02-29 13:36 ` Karel Zak [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=20120229133619.GA8471@x2.net.home \
--to=kzak@redhat.com \
--cc=bernhard.voelker@siemens-enterprise.com \
--cc=dave@gnu.org \
--cc=util-linux@vger.kernel.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