linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyson Nottingham <tgnottingham@gmail.com>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org, Tyson Nottingham <tgnottingham@gmail.com>
Subject: [PATCH 0/5] e2fsprogs: Update man pages, usage texts, and docs.
Date: Wed, 13 Dec 2017 23:13:08 -0800	[thread overview]
Message-ID: <cover.1513233071.git.tgnottingham@gmail.com> (raw)

These patches add missing feature descriptions and command arguments to
man pages and usage texts. They also fix some minor typos.

I'm just getting familiar with ext4, and this is the first patch series
I've sent to a mailing list, so I expect there to be issues. Please let
me know of any.

The patches are based off of the master branch of e2fsprogs. Should I be
working from a different branch? Also, I did not update any of the
localization files. Do I need to worry about handling that?

Thanks,
Tyson

Tyson Nottingham (5):
  Add missing features and mount options to ext4 man page.
  Add missing information to e2fsck man pages and usage text.
  Add missing information to debugfs man pages and usage texts.
  Add missing information to various man pages and usage texts.
  Fix minor typos in libext2fs documentation.

 debugfs/debugfs.8.in    |  49 +++++++++++++---
 debugfs/debugfs.c       |  10 ++--
 debugfs/do_journal.c    |   2 +-
 debugfs/logdump.c       |   2 +-
 debugfs/ls.c            |   2 +-
 debugfs/set_fields.c    |   4 +-
 debugfs/xattrs.c        |   2 +-
 doc/libext2fs.texinfo   |  16 +++---
 e2fsck/e2fsck.8.in      |  25 +++++----
 e2fsck/e2fsck.conf.5.in |  21 ++++++-
 e2fsck/unix.c           |   1 +
 misc/badblocks.c        |   2 +-
 misc/chattr.1.in        |   2 +-
 misc/e2image.8.in       |   2 +-
 misc/e2image.c          |   2 +-
 misc/e2undo.8.in        |  18 ++++++
 misc/e2undo.c           |   2 +-
 misc/e4crypt.8.in       |   8 +--
 misc/e4crypt.c          |   4 +-
 misc/ext4.5.in          | 146 +++++++++++++++++++++++++++++++++---------------
 misc/lsattr.1.in        |   4 +-
 misc/mke2fs.8.in        |   9 +++
 misc/mke2fs.conf.5.in   |  78 ++++++++++++--------------
 misc/tune2fs.8.in       |  33 +++++++----
 misc/tune2fs.c          |   6 +-
 resize/main.c           |   3 +-
 26 files changed, 300 insertions(+), 153 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-12-14  7:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  7:13 Tyson Nottingham [this message]
2017-12-14  7:13 ` [PATCH 1/5] Add missing features and mount options to ext4 man page Tyson Nottingham
2017-12-14 19:59   ` Theodore Ts'o
2017-12-14  7:13 ` [PATCH 2/5] Add missing information to e2fsck man pages and usage text Tyson Nottingham
2017-12-15  4:44   ` Theodore Ts'o
2017-12-14  7:13 ` [PATCH 3/5] Add missing information to debugfs man pages and usage texts Tyson Nottingham
2017-12-15  4:50   ` Theodore Ts'o
2017-12-14  7:13 ` [PATCH 4/5] Add missing information to various " Tyson Nottingham
2017-12-21 16:11   ` Theodore Ts'o
2017-12-14  7:13 ` [PATCH 5/5] Fix minor typos in libext2fs documentation Tyson Nottingham
2017-12-21 16:12   ` Theodore Ts'o
2017-12-14 17:24 ` [PATCH 0/5] e2fsprogs: Update man pages, usage texts, and docs Theodore Ts'o

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=cover.1513233071.git.tgnottingham@gmail.com \
    --to=tgnottingham@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).