Go to file
Karel Zak 167a2b520a sfdisk: fix logical partition resize when start specified
Addresses: https://github.com/karelzak/util-linux/issues/745
Signed-off-by: Karel Zak <kzak@redhat.com>
2019-01-31 14:16:42 +01:00
Documentation docs: update TODO 2019-01-18 11:14:38 +01:00
bash-completion bash-completion: umount support relative path and ~ as home shorthands 2019-01-12 19:29:37 +00:00
config build-sys: gtkdoc-fixxref v1.27 requires module option 2018-02-01 13:23:40 +01:00
disk-utils swapon: rewrite section about swapfiles 2019-01-22 10:02:17 +01:00
include lib/loopdev: set blocksize when create a new device 2019-01-22 11:37:35 +01:00
lib lib/loopdev: set blocksize when create a new device 2019-01-22 11:37:35 +01:00
libblkid libblkid: remove dependence on libuuid 2019-01-22 12:33:19 +01:00
libfdisk sfdisk: fix logical partition resize when start specified 2019-01-31 14:16:42 +01:00
libmount libmount: add support for MS_REMOUNT on --all 2019-01-16 15:00:07 +01:00
libsmartcols libsmartcols: remove extra ';' outside of a function [-Wextra-semi] 2019-01-02 14:40:30 +01:00
libuuid libuuid: fix man page typos 2018-12-10 12:47:50 +01:00
login-utils last: fix wtmp user name buffer overflow [asan] 2019-01-13 20:00:38 +00:00
m4 misc: fix typos using codespell 2018-02-16 11:12:52 +01:00
misc-utils logger: (man) add info about rewrite and authors 2019-01-29 15:59:41 +01:00
po po: merge changes 2018-11-06 12:00:00 +01:00
schedutils man: Use the correct macro for a font change of one argument 2018-05-23 10:43:27 +02:00
sys-utils setarch: don't return address of automatic variable 2019-01-22 12:02:16 +01:00
term-utils agetty: Return old behavior with empty logname 2018-11-21 10:48:05 +01:00
tests Removed BlueStore VERSION information as it is gibberish 2018-12-17 20:21:32 -06:00
text-utils hexdump: fix potential null pointer dereference warnings 2018-12-10 21:48:00 +00:00
tools tools: improve checkmans 2018-03-01 13:52:07 +01:00
.editorconfig add .editorconfig 2016-01-25 00:12:14 +01:00
.gitignore choom: new command to adjust OOM-killer score value 2018-04-16 12:53:39 +02:00
.travis-functions.sh travis: homebrew/dupes was deprecated 2018-03-09 09:57:23 +01:00
.travis.yml docs: add info about branches; update travis.yml 2018-10-24 13:02:59 +02:00
AUTHORS docs: update AUTHORS file 2018-11-06 12:03:34 +01:00
Makefile.am build: use --runstatedir instead of --localstatedir 2017-07-31 15:24:46 +02:00
NEWS build-sys: release++ (v2.33) 2018-11-06 12:08:46 +01:00
README docs: add link to mail list archive 2018-12-17 10:16:22 +01:00
README.licensing docs: use SPDX license names 2018-08-16 14:47:21 +02:00
autogen.sh build-sys: improve bison version detection 2018-04-30 09:43:32 +02:00
configure.ac build-sys: fix crypt() detection without -lcrypt 2019-01-23 12:20:47 +01:00
util-linux.doap docs: replace FTP by HTTPS in kernel.org URLs 2016-12-19 11:22:26 +01:00



		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
      ARCHIVE: https://lore.kernel.org/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.