Clone or download
karelzak build-sys: release++ (v2.33-rc2)
Signed-off-by: Karel Zak <>
Latest commit 3f7e7e4 Oct 19, 2018
Failed to load latest commit information.
Documentation docs: update v2.33-ReleaseNotes Oct 19, 2018
bash-completion bash-completion: cleanup mount and umount --namespace Oct 5, 2018
config build-sys: gtkdoc-fixxref v1.27 requires module option Feb 1, 2018
disk-utils sfdisk: disable --activate for Hybrid GPT/MBR Oct 4, 2018
include include/c: add str2memcpy() and mem2strcpy() Oct 3, 2018
lib lib/strutils: return from xstrmode() Sep 14, 2018
libblkid docs: use SPDX license names Aug 16, 2018
libfdisk libfdisk: fix printf format modifier Oct 4, 2018
libmount libmount: keep namespaces support optional Oct 5, 2018
libsmartcols libsmartcols: don't mark as extreme where average is zero Aug 23, 2018
libuuid libuuid: fix name-based UUIDs Aug 31, 2018
login-utils su: cleanup code to copy to log strings Oct 3, 2018
m4 misc: fix typos using codespell Feb 16, 2018
misc-utils rename: avoid undefined function prototype for `fpurge` Oct 4, 2018
po po: merge changes Oct 19, 2018
schedutils man: Use the correct macro for a font change of one argument May 23, 2018
sys-utils mount: add note about MS_BIND and _netdev Oct 2, 2018
term-utils agetty: don't use __u32 Oct 11, 2018
tests tests: add choom to build-sys test Sep 24, 2018
text-utils more: rename functions Sep 2, 2018
tools tools: improve checkmans Mar 1, 2018
.editorconfig add .editorconfig Jan 24, 2016
.gitignore choom: new command to adjust OOM-killer score value Apr 16, 2018 travis: homebrew/dupes was deprecated Mar 9, 2018
.travis.yml travis: enable osx root checks Mar 7, 2018
AUTHORS docs: update AUTHORS file Oct 19, 2018
COPYING docs: corrections to FSF license files, and postal address Feb 24, 2012
ChangeLog build-sys: use AUTOMAKE_OPTIONS = gnu May 26, 2011 build: use --runstatedir instead of --localstatedir Jul 31, 2017
NEWS build-sys: release++ (v2.33-rc2) Oct 19, 2018
README docs: add information about mailing list rejection Jun 1, 2017
README.licensing docs: use SPDX license names Aug 16, 2018 build-sys: improve bison version detection Apr 30, 2018 build-sys: release++ (v2.33-rc2) Oct 19, 2018
util-linux.doap docs: replace FTP by HTTPS in URLs Dec 19, 2016



		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.