summaryrefslogtreecommitdiffstats
path: root/Documentation
Commit message (Collapse)AuthorAgeFilesLines
* docs: grammarize the usage howtoBenno Schulenberg2014-05-061-80/+78Star
| | | | Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
* docs: update TODOKarel Zak2014-04-231-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: add pid alis to deprecated.txtKarel Zak2014-04-071-0/+7
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* lib/tt.c: Goodbye!Ondrej Oprala2014-04-031-3/+2Star
| | | | Signed-off-by: Ondrej Oprala <ooprala@redhat.com>
* docs: add a new command boilerplate codeSami Kerola2014-03-121-0/+100
| | | | | | | Having howtos is good, having an working code that can be used as-is to kickstart a write of a new command is better. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* docs: refresh TODOKarel Zak2014-02-271-9/+3Star
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* mkfs: mark this wrapper as DEPRECATEDKarel Zak2014-02-211-0/+3
| | | | | | | | | | | | | | | | | Theodore Ts'o: I'll add that I've never been convinced that the mkfs front end is all that useful. It's probably better for people to explicitly run /sbin/mkfs.xfs, /sbin/mkfs.ext4, etc.., so you don't have to worry about which options get passed down to the file system specific mkfs program, and which ones are interpreted by /sbin/mkfs --- and I don't believe /sbin/mkfs adds enough (err, any?) value that using "/sbin/mkfs -t xxx" vs "/sbin/mkfs.xxx" makes any sense whatsoever. ... and I absolutely agree. Reported-by: Theodore Ts'o <tytso@mit.edu> Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: add lslogins(1) to TODOKarel Zak2014-01-141-0/+11
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: update links to http://git.kernel.org/ web repository viewsSami Kerola2013-11-121-1/+1
| | | | Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* docs: add patching process to howto-contribute.txtSami Kerola2013-11-121-0/+23
| | | | Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* docs: add note about make distcheckKarel Zak2013-11-081-0/+2
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: update TODO, wipe check for fdisk already implementedKarel Zak2013-10-231-3/+0Star
| | | | | | | Note that rather than implement wipe command in fdisk it's better inform users to call wipefs(8). Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: update v2.24-ReleaseNotesKarel Zak2013-10-211-1/+37
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: update TODOKarel Zak2013-10-181-0/+3
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: update TODOKarel Zak2013-10-161-2/+10
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: mention in ReleaseNotes only PO files that were actually updatedBenno Schulenberg2013-10-141-9/+9
| | | | | | Also tweak wording a bit and remove a duplicate line. Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
* docs: update v2.24-ReleaseNotesKarel Zak2013-10-111-1/+89
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: improve grammar and wording of the release-schedule textBenno Schulenberg2013-10-081-22/+23
| | | | Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
* docs: update TODOKarel Zak2013-10-021-25/+4Star
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* nologin: add new commandKarel Zak2013-09-301-0/+4
| | | | | | | Currently it's maintained as distro specific (or people use impolite /bin/false way). Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: update v2.24-ReleaseNotesKarel Zak2013-09-271-1/+13
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: add v2.24-ReleaseNotesKarel Zak2013-09-261-0/+784
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* fdisk: mark -s option as deprecatedKarel Zak2013-09-161-0/+5
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: add CFLAGS and LDFLAGS for daemons and shared libsKarel Zak2013-08-271-5/+5
| | | | | | | | This is necessary for paranoid security guys who believe that things like "-Wl,-z,relro" or "-Wl,-z,bind_now" is a way how to make the world a safer place... Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: be clear which last(1) is deprecatedSami Kerola2013-08-231-1/+1
| | | | | | The recently merged sysvinit last(1) and lastb(1) are supported. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* build-sys: complete elvtune removalSami Kerola2013-08-231-5/+0Star
| | | | | | | | The first removal managed to remove only most of the elvtune, this commit will complete the task. Original-removal: 7f1fe74248290c50f5447c2c09fcf0f0575a7666 Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* docs: update TODOSami Kerola2013-08-231-5/+0Star
| | | | | | | The minix type fixes took place December 2012. Commit: a180dc6c54f90896d6491f9bdf704523236dd99c Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* util-linux minor typo fixesGilles Espinasse2013-05-211-1/+1
| | | | Signed-off-by: Gilles Espinasse <g.esp@free.fr>
* docs: note ddate removalMike Frysinger2013-05-061-0/+3
| | | | Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* docs: update v2.23-ReleaseNotesKarel Zak2013-04-251-6/+49
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: update v2.23-ReleaseNotesKarel Zak2013-04-101-1/+150
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* libblkid: support LIBBLKID_DEBUG= onlyKarel Zak2013-04-091-0/+3
| | | | | | ... the BLKID_DEBUG= is not more supported. Signed-off-by: Karel Zak <kzak@redhat.com>
* Spelling fixes.Ville Skyttä2013-04-081-1/+1
| | | | Signed-off-by: Ville Skyttä <ville.skytta@iki.fi>
* bash-completion: add completion files to Makefile.amSami Kerola2013-04-011-3/+4
| | | | | | And remove shell completion TODO item. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* docs: add note about /var/lib/hwclock to TODOKarel Zak2013-03-261-0/+7
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: arch is gone, use delpart as usage() function exampleSami Kerola2013-03-261-1/+1
| | | | | | The arch.c was removed in commit 27abd809. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* docs: upadte v2.23-ReleaseNotesKarel Zak2013-03-221-10/+8Star
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: add v2.23-ReleaseNotesKarel Zak2013-03-221-0/+976
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: add wipefs feature request to TODOKarel Zak2013-03-191-0/+5
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: cleanup TODOKarel Zak2013-03-181-23/+15Star
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* chkdupexe: remove, deprecated for yearsKarel Zak2013-03-141-6/+0Star
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* arch: remove the command, deprecated since 2.13, use coreutils versionKarel Zak2013-03-141-8/+0Star
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: update deprecated.txtKarel Zak2013-02-261-0/+11
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* textual: spell and encode the name of Arkadiusz Miśkiewicz correctlyBenno Schulenberg2013-02-064-4/+4
| | | | Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
* docs: usage function and gettextSami Kerola2013-01-251-3/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I made following survey which was sent to all email addresses in po/ directory that had the on-going millenium as time when translator had been active. There are two quite common styles to write a command usage print out, which one you prefer? 1. Each option as separated translatable string. 18 votes 2. Or the whole thing as one big output. 1 vote 3. No preference. 1 vote The questionaire had also free text field asking 'Why do you prefer that?', and here are the answers. [Separately] It is easier to follow changes with the translations. If you change only one line or two, the big string would change to fuzzy and I have to check the whole thing to see what was changed in the original. If the changed line is a single string, the string to check is a lot shorter. [No preference] Usually, if there is no reason to separate strings, better keep them together so that the context is obvious. In the case at hand, it might help if in some language e.g. one translated line is too wide for the screen. This is unlikely, but... OTOH, with this solution, if you change one string the whole translation will be discarded until a translator comes and updates it... [Separately] It may be a bit harder to get the formatting right, but it is much easier in maintenance. With one option changing, the translator immediately sees the spot. And even with a lazy translator, program author will have all the options translated that have not changed at all. [Separately] First one would be more in elegant I believe [Separately] I prefer to have them separately because they don't form a single text paragraph. In other words, they can be translated separately because they are complete and separate "sentences". Of course consistency of format and word choices need to be taken care of, but the fact that the messages appear next to each other in the PO file should be enough. Also if the options are not translated separately, adding or editing one option causes the translation of all options to become fuzzy and if for some reason it isn't checked before next release (happens sometimes), all of them will show untranslated to the user. [Separately] Translations are a lot easier to update that way. If an option is added, removed or changed, only a small amount of text becomes fuzzy. If everything is in one big output, a lot of text becomes fuzzy, and you have to read a lot more text to discover what exactly changed. [Separately] When updating a fuzzy translation, with one big output it's very tedious and error-prone to find out the reason for fuzziness, i.e. what actually has changed in the msgid. [Separately] Way easier to translate, and especially to spot translation updates when one string gets removed, added or modified. [Separately] Makes translation memory more efficient. Some hard terms in the list don't prevent translation of the whole block. Actually the beginning of the strings don't need any translation ta all before [] part. Information about the context can be provided in comments or the context parameter. [Separately] Please consider the case when a part of string, (= msgid) is changed. It is marked as fuzzy in the .po files, we translators have to check whole sentences for the difference between it and previous version. [Separately] Every sentence must be a separate translation unit. [One big output] for performance to ouput strings [Separately] In the second case, if only one option changes (or a new one is added), the translator will see as if all of the options changed, having to find out which one of them is really new or has actually changed. Also, if the translator has had no time to update the string, only one of the options will be shown in the original language (which is arguably ugly, but better than nothing for many users). [Separately] It's easier to translate the options separately using translation memory. [Separately] Easier to separate and see changes [Separately] more translator friendly [Separately] From the user POV I found the separeted version more interesting because if a maintainer can't update the translation fast enough between releases the user will still get the current translated string with the new ones untraslated. From the translator POV the big output will give more context information as one can see the whole command options. With a new string added while the rest is translated having some context can be more difficult. [Separately] Additions to the list or changes to one options means you don't have to check all lines each time. So unless you have very, _very_ good reason you should not output all usage as one big table. This implies also that when large usage output is changed it should be split to small hunks. That may be a bit more work once, but the next change will pay the extrawork off so never hesitate when splitting. Reference: http://www.surveymonkey.com/s/QKZ75HK Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* mount: add support for x-mount.mkdir[=<mode>] optionOndrej Oprala2013-01-091-2/+0Star
| | | | | | | | | If the target directory (mountpoint) does not exist then mount(8) will create it before mount.<type> is executed or mount(2) syscall is called. Co-Author: Karel Zak <kzak@redhat.com> Signed-off-by: Ondrej Oprala <ooprala@redhat.com> Signed-off-by: Karel Zak <kzak@redhat.com>
* tunelp: deprecation: remove command from default buildSami Kerola2012-12-191-0/+4
| | | | | | It is difficult to think think tunelp command being in use a lot. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* Merge branch '2012wk47' of git://github.com/kerolasa/lelux-utiliteetitKarel Zak2012-11-303-76/+41Star
|\
| * docs: ddate removalSami Kerola2012-11-251-73/+0Star
| | | | | | | | | | | | Missed in commit 4cf02b65109029a38f708148dea8d2bdf2fa19de Signed-off-by: Sami Kerola <kerolasa@iki.fi>
| * docs: mention what Open Group has marked legacySami Kerola2012-11-251-0/+12
| | | | | | | | | | Reviewed-by: Bruce Dubbs <bruce.dubbs@gmail.com> Signed-off-by: Sami Kerola <kerolasa@iki.fi>
generated by cgit v1.2.3-55-g7522 (git 2.39.0) at 2024-06-27 04:08:46 +0200