linux-ext4 - Re: [PATCH 0/5] e2fsprogs: Update man pages, usage texts, and docs.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 14 Dec 2017 12:24:33 -0500
From:   Theodore Ts'o <tytso@....edu>
To:     Tyson Nottingham <tgnottingham@...il.com>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: [PATCH 0/5] e2fsprogs: Update man pages, usage texts, and docs.

On Wed, Dec 13, 2017 at 11:13:08PM -0800, Tyson Nottingham wrote:
> These patches add missing feature descriptions and command arguments to
> man pages and usage texts. They also fix some minor typos.

Thanks so much for working on the e2fsprogs documentation!  It is an
often an underappreciated work, and I'm glad to have someone working
to improve the documentation.

> 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?

The maint branch corresponds to the 1.43.x release series, and the
master and next branches present what will (soon) become the 1.44(.x)
release.  There will be at least one more 1.43.x release before I
release 1.44, so it's not that of an issue.

I can handle trying to apply these patches to the maint branch,
pulling out the feature improvements that only appear in the master
branch and applying that in a separate patch for the master branch.
But in the future, it would be preferable for bug fixes and doc fixes
to be done against the maint branch (if applicable).  The master/next
branch will get fixes via git merges.

Cheers,

					- Ted