C Roff Shell M4 Yacc Makefile Python
Latest commit 9e33cdd Oct 17, 2017 @kerolasa kerolasa committed with karelzak rfkill: fix description name typo
Commit 7d2a996 made gps to look like a GUID Partition Table.

Reviewed-by: Karel Zak <kzak@redhat.com>
Signed-off-by: Sami Kerola <kerolasa@iki.fi>
Failed to load latest commit information.
Documentation setsid: document fork(2) usage Oct 10, 2017
bash-completion bash-completion: update uuidgen, wipefs, tunelp, setpriv, and hwclock Sep 18, 2017
config build-sys: inform gtk-doc about __ul_attribute__ Mar 15, 2013
disk-utils cfdisk: cleanup die-on-signal code Sep 26, 2017
include losetup: Add support for logical block size Sep 27, 2017
lib lib/pager: check open() return code [coverity scan] Oct 11, 2017
libblkid libfdisk: (sun) make math more robust [coverity scan] Oct 11, 2017
libfdisk build-sys: fix non-blkid compilation Sep 19, 2017
libmount libmount: make sure we call stat() propely [coverity scan] Oct 11, 2017
libsmartcols libsmartcols: (sample) cleanup line separator usage Oct 12, 2017
libuuid misc: cleanup UUID_STR_LEN definitions Sep 15, 2017
login-utils lslogins: fix possible memory leak [coverity scan] Oct 11, 2017
m4 build-sys: add libtinfow check Sep 19, 2017
misc-utils blkid: improve man page wording Oct 16, 2017
po po: merge changes Oct 3, 2017
schedutils misc: consolidate macro style USAGE_HELP_OPTIONS Jun 29, 2017
sys-utils rfkill: fix description name typo Oct 17, 2017
term-utils agetty: fix /etc/os-release parsing Oct 5, 2017
tests tests: update build-sys tests Sep 19, 2017
text-utils column: (-t) disable encoding for non-printable chars Jul 31, 2017
tools tools: add segfault detection for checkusage.sh Jun 29, 2017
.editorconfig add .editorconfig Jan 24, 2016
.gitignore rfkill: make command to build in util-linux project Aug 30, 2017
.travis-functions.sh travis: add make checkusage Jun 27, 2017
.travis.yml travis: minor cosmetics Jun 15, 2017
AUTHORS docs: update AUTHORS file Oct 3, 2017
COPYING docs: corrections to FSF license files, and postal address Feb 24, 2012
ChangeLog build-sys: use AUTOMAKE_OPTIONS = gnu May 26, 2011
Makefile.am build: use --runstatedir instead of --localstatedir Jul 31, 2017
NEWS build-sys: release++ (v2.31-rc2) Oct 3, 2017
README docs: add information about mailing list rejection Jun 1, 2017
README.licensing COPYING: fix grammar of referring phrase, and indicate location better Oct 8, 2013
autogen.sh build-sys: add parse-date.y Mar 4, 2017
configure.ac build-sys: release++ (v2.31-rc2) Oct 3, 2017
util-linux.doap docs: replace FTP by HTTPS in kernel.org 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".


      E-MAIL: util-linux@vger.kernel.org
      URL:    http://vger.kernel.org/vger-lists.html#util-linux

      The mailing list will reject email messages that contain:
       - more than 100K characters
       - html
       - spam phrases/keywords
      See: http://vger.kernel.org/majordomo-info.html#taboo


      #util-linux at freenode.net:


      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.


      E-MAIL: util-linux@vger.kernel.org
      Web:    https://github.com/karelzak/util-linux/issues

      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://git.kernel.org/pub/scm/utils/util-linux/util-linux.git

    Backup repository:
	  git clone git://github.com/karelzak/util-linux.git

    Web interfaces:

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

      The kernel.org 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.