From: Davidlohr Bueso <dave@gnu.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: [PATCH] docs: update TODO file
Date: Wed, 26 Oct 2011 16:26:49 +0200 [thread overview]
Message-ID: <1319639209.3771.14.camel@offworld> (raw)
From: Davidlohr Bueso <dave@gnu.org>
Signed-off-by: Davidlohr Bueso <dave@gnu.org>
---
Documentation/TODO | 11 -----------
1 files changed, 0 insertions(+), 11 deletions(-)
diff --git a/Documentation/TODO b/Documentation/TODO
index 2a4ab22..583a96a 100644
--- a/Documentation/TODO
+++ b/Documentation/TODO
@@ -1,10 +1,6 @@
Note that items with (!) have high priority.
-prlimit
--------
- - add new command line wrapper for prlimit(2)
-
dmesg
-----
@@ -96,13 +92,6 @@ libblkd and libmountL
partx
-----
- - (!) add support loop devices:
-
- partx -a /path/file.img
-
- * associate the file with loop device (use lib/loopdev.c)
- * map partitions by BLKPG_ADD_PARTITION
-
- support mapping by device-mapper if argv[0] is "kpartx" or --dm option is used.
- (!) add regression tests for partx, addpart and delpart
--
1.7.7
next reply other threads:[~2011-10-26 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 14:26 Davidlohr Bueso [this message]
2011-11-02 15:25 ` [PATCH] docs: update TODO file Karel Zak
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=1319639209.3771.14.camel@offworld \
--to=dave@gnu.org \
--cc=kzak@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).