Util-Linux package development
 help / color / mirror / Atom feed
From: Sami Kerola <kerolasa@iki.fi>
To: util-linux@vger.kernel.org
Cc: Sami Kerola <kerolasa@iki.fi>
Subject: [PATCH 00/12] pull: minix updates
Date: Wed, 24 Jun 2015 09:15:07 +0100	[thread overview]
Message-ID: <1435133719-2971-1-git-send-email-kerolasa@iki.fi> (raw)

Hi all,

The patch 0001 is not re-submitted.  It is the change Joshua Hudson sent
to mail list couple days ago.  The rest are new changes, and they are
also available from my remote branch 'minix'.

The following changes since commit 4b7248c0296e94fc1d85c22bbad5f7b943689971:
  libfdisk: add GPT GUIDs for ARMs (2015-06-22 11:56:43 +0200)
are available in the git repository at:
  git://github.com/kerolasa/lelux-utiliteetit.git minix
for you to fetch changes up to d60409ed753acb02fa1ea382e0c638d378653448:
  docs: make fsck.minix(8) more pretty (2015-06-24 09:10:20 +0100)

Joshua Hudson (1):
  mkfs.minix: increase maximum minix v2 and v3 file system sizes

Sami Kerola (11):
  mkfs.minix: introduce long options to the command
  mkfs.minix: use is_mounted() from libcommon
  mkfs.minix: remove unuseful code
  mkfs.minix: add fs_control structure, and remove most global variables
  mkfs.minix: check user input carefully
  mkfs.minix: check requested blocks will not exceed available on device
  mkfs.minix: refactor root block content creation
  fsck.minix: rename device file descriptor variable
  fsck.minix: add minix v3 support
  fsck.minix: introduce long options to the command
  docs: make fsck.minix(8) more pretty

 bash-completion/fsck.minix |  12 +-
 bash-completion/mkfs.minix |  16 +-
 disk-utils/fsck.minix.8    | 159 +++++++-----
 disk-utils/fsck.minix.c    | 223 ++++++++--------
 disk-utils/mkfs.minix.8    |  37 +--
 disk-utils/mkfs.minix.c    | 623 +++++++++++++++++++++++----------------------
 6 files changed, 567 insertions(+), 503 deletions(-)

-- 
2.4.4


             reply	other threads:[~2015-06-24  8:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  8:15 Sami Kerola [this message]
2015-06-24  8:15 ` [PATCH 01/12] mkfs.minix: increase maximum minix v2 and v3 file system sizes Sami Kerola
2015-06-24  8:15 ` [PATCH 02/12] mkfs.minix: introduce long options to the command Sami Kerola
2015-06-24  8:15 ` [PATCH 03/12] mkfs.minix: use is_mounted() from libcommon Sami Kerola
2015-06-24  8:15 ` [PATCH 04/12] mkfs.minix: remove unuseful code Sami Kerola
2015-06-24  8:15 ` [PATCH 05/12] mkfs.minix: add fs_control structure, and remove most global variables Sami Kerola
2015-06-24  8:15 ` [PATCH 06/12] mkfs.minix: check user input carefully Sami Kerola
2015-06-24  8:15 ` [PATCH 07/12] mkfs.minix: check requested blocks will not exceed available on device Sami Kerola
2015-06-24  8:15 ` [PATCH 08/12] mkfs.minix: refactor root block content creation Sami Kerola
2015-06-24  8:15 ` [PATCH 09/12] fsck.minix: rename device file descriptor variable Sami Kerola
2015-06-24  8:15 ` [PATCH 10/12] fsck.minix: add minix v3 support Sami Kerola
2015-06-24  8:15 ` [PATCH 11/12] fsck.minix: introduce long options to the command Sami Kerola
2015-06-24  8:15 ` [PATCH 12/12] docs: make fsck.minix(8) more pretty Sami Kerola
2015-07-30  9:55 ` [PATCH 00/12] pull: minix updates Karel Zak
2015-07-30 10:31   ` Sami Kerola

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=1435133719-2971-1-git-send-email-kerolasa@iki.fi \
    --to=kerolasa@iki.fi \
    --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