On Thu, Jul 21, 2011 at 17:43, Karel Zak <kzak@xxxxxxxxxx> wrote: > The 'ioprio' in the syscall: > > syscall(SYS_ioprio_set, which, who, ioprio); > > encodes two information: > > IOPRIO_PRIO_CLASS - e.g. realtime, idle, ... > IOPRIO_PRIO_DATA - e.g. 0-7 > > this is reason why the docs is talking about "class" and "class data". > > Anyway, merged with some minor changes and --classdata option :-) Sounds reasonable. > Minor notes: > > * .PP in man page within .IP block does not have the same meaning > like blank line Oops, that was sloppy from my side. Sorry. > * I think that > -c, --class NUM > is better than > -c, --class=NUM With equals sign is FSFism, which seemed like good starting point... > I have fixed this in ionice man page, but not in usage(). It would be > nice to use in all man pages and usage() functions the same syntax. > Maybe we can create any template or so to have it documented. ...but you are absolutely right again. Converting README.devel in small chunks to a Documentation directory might be a way to go. Contents of the directory could have help_and_version.txt for what you said above, and I can recall recent minix & kernel headers conversation which ought also be documented. BTW what would you think about having a util-linux.h with inline function to print in usage help & version option descriptions and proper version output function. The first would make translation teams happier when they do not need to write time after time the same translations. Second would simply unify how version is printed, and if it ever needs a modification it's easier to do. In practice the file would be similar to coreutils system.h. http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=blob;f=src/system.h -- Sami Kerola http://www.iki.fi/kerolasa/ -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
