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 634446308f pipesz: fix dead code [coverity scan] 5 days ago
.github/workflows ci: add a GHAction sending data to Coverity 7 months ago
Documentation docs: update v2.38-ReleaseNotes 2 months ago
bash-completion pipesz: add bash-completion script 6 days ago
config build-sys: gtkdoc-fixxref v1.27 requires module option 4 years ago
disk-utils fix various formats 2 weeks ago
include pipesz: add the pipesz utility 6 days ago
lib fix various formats 2 weeks ago
libblkid fix various formats 2 weeks ago
libfdisk meson: fix static builds creating conflicting targets 1 month ago
libmount libmount: fix and improve utab update on MS_MOVE 3 weeks ago
libsmartcols meson: fix typoed copy-paste error that override other dependencies to blkid 1 month ago
libuuid libuuid: improve cache handling 4 weeks ago
login-utils libmount: fix typos 2 months ago
m4 build-sys: use $LIBS rather than LDFLAGS 11 months ago
man-common colors.adoc: format command name bold 3 months ago
misc-utils pipesz: fix dead code [coverity scan] 5 days ago
po meson: don't build po if no gettext 6 days ago
po-man Add blkpr.8.adoc to po4a configuration 3 weeks ago
schedutils man pages: unify output of --help and --version 4 months ago
sys-utils Merge branch 'issue-1686' of 6 days ago
term-utils fix various formats 2 weeks ago
tests pipesz: add tests 6 days ago
text-utils more: avoid infinite loop on --squeeze 3 weeks ago
tools tools: add git-tp-sync-man 3 months ago
.editorconfig add .editorconfig 6 years ago
.gitignore pipesz: add the pipesz utility 6 days ago
AUTHORS docs: update AUTHORS file 2 months ago
COPYING docs: corrections to FSF license files, and postal address 10 years ago
ChangeLog docs: Correct ChangeLog URL to history log. 2 years ago build-sys: distribute Meson files 3 months ago
NEWS build-sys: release++ (v2.38) 2 months ago
README docs: update IRC address 7 months ago
README.licensing docs: add GPLv3 text 3 years ago build-sys: use set +e before patch --try in ./ 7 months ago pipesz: add the pipesz utility 6 days ago pipesz: add bash-completion script 6 days ago
meson_options.txt pipesz: add the pipesz utility 6 days ago
util-linux.doap docs: update github URL 7 months ago



util-linux is a random collection of Linux utilities

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


See Documentation/howto-compilation.txt.



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.



Bug reports with sensitive or private information: Karel Zak <>

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:

See also:

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.