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 a61955ba1f lib/loopdev: cosmetic changes to LOOP_CONFIGURE 2 years ago
.github/workflows cifuzz: turn on MSan 2 years ago
Documentation column: Deprecate --table-empty-lines in favor of --keep-empty-lines 2 years ago
bash-completion column: Deprecate --table-empty-lines in favor of --keep-empty-lines 2 years ago
config build-sys: gtkdoc-fixxref v1.27 requires module option 5 years ago
disk-utils fdisk: always report fdisk_create_disklabel() errors 2 years ago
include lib/loopdev: cosmetic changes to LOOP_CONFIGURE 2 years ago
lib lib/loopdev: cosmetic changes to LOOP_CONFIGURE 2 years ago
libblkid libblkid: (gpt) accept tiny devices 2 years ago
libfdisk libfdisk: (gpt) reduce number of entries to fit small device 2 years ago
libmount libmount: optimize mnt_optstr_apply_flags() 2 years ago
libsmartcols libsmartcols: don't print empty output on empty table in JSON 2 years ago
libuuid libuuid: (test) make sure UUID is terminated [coverity scan] 2 years ago
login-utils login: use mem2strcpy() rather than rely on printf() 2 years ago
m4 build-sys: add missing NR underscore to UL_CHECK_SYSCALL() 3 years ago
misc-utils lsblk: fix SCSI_IDENT_SERIAL 2 years ago
po po: update fr.po (from 2 years ago
schedutils chrt: don't restrict --reset-on-fork, add more info to man page 2 years ago
sys-utils Merge branch 'frkaya/loopconfig' of 2 years ago
term-utils agetty: fix typo in manual page 2 years ago
tests Merge branch 'col-refactor' of 2 years ago
text-utils col: enable deallocation on exit also for __SANITIZE_ADDRESS__ 2 years ago
tools tests: add a fuzz target calling fdisk_script_read_file 2 years ago
.editorconfig add .editorconfig 7 years ago
.gitignore lsirq: add new command 3 years ago travis: stop building fuzz targets on macOS 2 years ago
.travis.yml Merge branch 'coverity' of 2 years ago
AUTHORS docs: update AUTHORS file 2 years ago
COPYING docs: corrections to FSF license files, and postal address 11 years ago
ChangeLog docs: Correct ChangeLog URL to history log. 2 years ago build-sys: add support for --enable-fuzzing-engine 2 years ago
NEWS build-sys: release++ (v2.36) 2 years ago
README docs: add link to mail list archive 4 years ago
README.licensing docs: add GPLv3 text 3 years ago build-sys: improve bison version detection 5 years ago mkswap: check for holes and unwanted extentd in file 2 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.