From: Michal Soltys <soltys-R61QfzASbfY@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] 99fs-lib module for common fsck needs
Date: Thu, 14 Jul 2011 23:59:45 +0200 [thread overview]
Message-ID: <4E1F66D1.3010107@ziu.info> (raw)
In-Reply-To: <1307049735-2345-1-git-send-email-soltys-R61QfzASbfY@public.gmane.org>
So any comments about this idea ?
Anything to change ? Or just drop this approach as too much for this stage ?
next prev parent reply other threads:[~2011-07-14 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 21:22 [PATCH] 99fs-lib module for common fsck needs Michal Soltys
[not found] ` <1307049735-2345-1-git-send-email-soltys-R61QfzASbfY@public.gmane.org>
2011-06-02 21:22 ` [PATCH 1/4] implement fs-lib, squash a few bugs that were part of det_fs/wrap_fsck Michal Soltys
2011-06-02 21:22 ` [PATCH 2/4] 95rootfs-block/mount-root.sh: '-a' for ext? is handled in fs-lib now Michal Soltys
2011-06-02 21:22 ` [PATCH 3/4] 95rootfs-block/mount-root.sh: squash rootopts into rflags Michal Soltys
2011-06-02 21:22 ` [PATCH 4/4] 95rootfs-block/mount-root.sh: comment out fstab generation Michal Soltys
2011-07-14 21:59 ` Michal Soltys [this message]
2011-08-12 6:22 ` [PATCH] 99fs-lib module for common fsck needs Harald Hoyer
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=4E1F66D1.3010107@ziu.info \
--to=soltys-r61qfzasbfy@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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