Go to file
Karel Zak 558880dd35 Merge branch 'frkaya/loopconfig' of https://github.com/franksinankaya/util-linux
* 'frkaya/loopconfig' of https://github.com/franksinankaya/util-linux:
  loopdev: use LOOP_CONFIG ioctl
2020-10-05 14:51:45 +02:00
.github/workflows cifuzz: turn on MSan 2020-08-06 15:36:45 +00:00
Documentation column: Deprecate --table-empty-lines in favor of --keep-empty-lines 2020-09-29 12:38:18 +02:00
bash-completion column: Deprecate --table-empty-lines in favor of --keep-empty-lines 2020-09-29 12:38:18 +02:00
config build-sys: gtkdoc-fixxref v1.27 requires module option 2018-02-01 13:23:40 +01:00
disk-utils fdisk: always report fdisk_create_disklabel() errors 2020-09-30 11:49:05 +02:00
include Merge branch 'frkaya/loopconfig' of https://github.com/franksinankaya/util-linux 2020-10-05 14:51:45 +02:00
lib Merge branch 'frkaya/loopconfig' of https://github.com/franksinankaya/util-linux 2020-10-05 14:51:45 +02:00
libblkid libblkid: (gpt) accept tiny devices 2020-09-30 13:11:01 +02:00
libfdisk libfdisk: (gpt) reduce number of entries to fit small device 2020-09-30 12:38:59 +02:00
libmount libmount: optimize mnt_optstr_apply_flags() 2020-09-29 12:31:06 +02:00
libsmartcols libsmartcols: don't print empty output on empty table in JSON 2020-09-07 11:52:13 +02:00
libuuid libuuid: (test) make sure UUID is terminated [coverity scan] 2020-07-14 12:15:47 +02:00
login-utils login: use mem2strcpy() rather than rely on printf() 2020-10-01 14:04:21 +02:00
m4 build-sys: add missing NR underscore to UL_CHECK_SYSCALL() 2019-11-25 20:33:05 +00:00
misc-utils lsblk: fix SCSI_IDENT_SERIAL 2020-09-24 09:56:03 +02:00
po po: update fr.po (from translationproject.org) 2020-07-23 11:25:41 +02:00
schedutils chrt: don't restrict --reset-on-fork, add more info to man page 2020-10-01 11:51:12 +02:00
sys-utils Merge branch 'frkaya/loopconfig' of https://github.com/franksinankaya/util-linux 2020-10-05 14:51:45 +02:00
term-utils agetty: fix typo in manual page 2020-10-03 11:57:56 +00:00
tests Merge branch 'col-refactor' of https://github.com/kerolasa/util-linux 2020-09-29 13:41:00 +02:00
text-utils col: enable deallocation on exit also for __SANITIZE_ADDRESS__ 2020-09-30 13:48:54 +02:00
tools tests: add a fuzz target calling fdisk_script_read_file 2020-08-10 23:30:50 +00:00
.editorconfig add .editorconfig 2016-01-25 00:12:14 +01:00
.gitignore lsirq: add new command 2020-03-06 16:21:10 +01:00
.travis-functions.sh travis: stop building fuzz targets on macOS 2020-08-11 00:21:27 +00:00
.travis.yml Merge branch 'coverity' of https://github.com/evverx/util-linux 2020-07-14 10:26:44 +02:00
AUTHORS docs: update AUTHORS file 2020-07-22 14:38:31 +02:00
COPYING docs: corrections to FSF license files, and postal address 2012-02-24 14:13:35 +01:00
ChangeLog docs: Correct ChangeLog URL to history log. 2020-05-11 09:48:43 +02:00
Makefile.am build-sys: add support for --enable-fuzzing-engine 2020-08-06 12:33:11 +00:00
NEWS build-sys: release++ (v2.36) 2020-07-23 11:26:04 +02:00
README docs: add link to mail list archive 2018-12-17 10:16:22 +01:00
README.licensing docs: add GPLv3 text 2019-11-08 11:10:54 +01:00
autogen.sh build-sys: improve bison version detection 2018-04-30 09:43:32 +02:00
configure.ac mkswap: check for holes and unwanted extentd in file 2020-09-09 11:10:51 +02: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.