You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Karel Zak 5db5962339 lib/colors: force to "never" mode on non-terminal output 4 years ago
Documentation docs: update TODO 4 years ago
bash-completion bash-completion: umount support relative path and ~ as home shorthands 4 years ago
config build-sys: gtkdoc-fixxref v1.27 requires module option 5 years ago
disk-utils swapon: rewrite section about swapfiles 4 years ago
include lib/colors: force to "never" mode on non-terminal output 4 years ago
lib lib/colors: force to "never" mode on non-terminal output 4 years ago
libblkid libblkid: remove dependence on libuuid 4 years ago
libfdisk sfdisk: fix logical partition resize when start specified 4 years ago
libmount libmount: add support for MS_REMOUNT on --all 4 years ago
libsmartcols libsmartcols: remove extra ';' outside of a function [-Wextra-semi] 4 years ago
libuuid libuuid: fix man page typos 4 years ago
login-utils last: fix wtmp user name buffer overflow [asan] 4 years ago
m4 misc: fix typos using codespell 5 years ago
misc-utils logger: (man) add info about rewrite and authors 4 years ago
po po: merge changes 4 years ago
schedutils man: Use the correct macro for a font change of one argument 4 years ago
sys-utils setarch: don't return address of automatic variable 4 years ago
term-utils agetty: Return old behavior with empty logname 4 years ago
tests Removed BlueStore VERSION information as it is gibberish 4 years ago
text-utils hexdump: fix potential null pointer dereference warnings 4 years ago
tools tools: improve checkmans 5 years ago
.editorconfig add .editorconfig 7 years ago
.gitignore choom: new command to adjust OOM-killer score value 5 years ago travis: homebrew/dupes was deprecated 5 years ago
.travis.yml docs: add info about branches; update travis.yml 4 years ago
AUTHORS docs: update AUTHORS file 4 years ago
COPYING docs: corrections to FSF license files, and postal address 11 years ago
ChangeLog build-sys: use AUTOMAKE_OPTIONS = gnu 12 years ago build: use --runstatedir instead of --localstatedir 5 years ago
NEWS build-sys: release++ (v2.33) 4 years ago
README docs: add link to mail list archive 4 years ago
README.licensing docs: use SPDX license names 4 years ago build-sys: improve bison version detection 5 years ago build-sys: fix crypt() detection without -lcrypt 4 years ago
util-linux.doap docs: replace FTP by HTTPS in URLs 6 years ago



util-linux is a random collection of Linux utilities

Note: for the years 2006-2010 this project was named "util-linux-ng".



The mailing list will reject email messages that contain:
- more than 100K characters
- html
- spam phrases/keywords


#util-linux at


The IRC channel and Mailing list are for developers and project
maintainers. For end users it is recommended to utilize the
distribution's support system.



This project has no resources to provide support for distribution specific
issues. For end users it is recommended to utilize the distribution's
support system.


PO files are maintained by:


Standard releases:
major = fatal and deep changes
minor = typical release with new features
maint = maintenance releases; bug fixes only

Development releases:


Download archive:

SCM (Source Code Management) Repository:

Primary repository:
git clone git://

Backup repository:
git clone git://

Web interfaces:

Note: the GitHub repository may contain temporary development branches too.

The repository contains master (current development) and stable/*
(maintenance) branches only. All master or stable/* changes are always pushed
to both repositories at the same time.

Repository Branches: 'git branch -a'
master branch
- current development
- the source for stable releases when deemed ready.
- day-to-day status is: 'it works for me'. This means that its
normal state is useful but not well tested.
- long-term development or invasive changes in active development are
forked into separate 'topic' branches from the tip of 'master'.

stable/ branches
- public releases
- branch name: stable/v<major>.<minor>.
- created from the 'master' branch after two or more release
candidates and the final public release. This means that the stable
releases are committed, tagged, and reachable in 'master'.
- these branches then become forked development branches. This means
that any changes made to them diverge from the 'master' branch.
- maintenance releases are part of, and belong to, their respective
stable branch. As such, they are tags(<major>.<minor>.<maint>) and
not branches of their own. They are not part of, visible in, or
have anything to do with the 'master' development branch. In git
terminology: maintenance releases are not reachable from 'master'.
- when initially cloned (as with the 'git clone' command given above)
these branches are created as 'remote tracking branches' and are
only visible by using the -a or -r options to 'git branch'. To
create a local branch use the desired tag with this command:
'git checkout -b v2.29.2 v2.29.2'

Tags: 'git tag'
- a new tag object is created for every release.
- tag name: v<version>.
- all tags are signed by the maintainer's PGP key.

Known Bugs:
- don't use tag v2.13.1 (created and published by mistake),
use v2.13.1-REAL instead.


1) development (branch: <master>)

2) master release (tags: v2.29-rc1, v2.29-rc2, v2.29, branch: <master>)

3) development (work on v2.30, branch: <master>)

4) fork -- create a new branch <stable/v2.29> based on tag v2.29

4a) new patches or cherry-pick patches from <master> (branch: <stable/v2.29>)

4b) stable release (tag: v2.29.1, branch: <stable/v2.29>)

4c) more patches; another release (tag: v2.29.2, branch: <stable/v2.29>)

5) master release v2.30 (branch: <master>)

where 3) and 4) happen simultaneously.