Go to file
Karel Zak ee2d371c61 include/fileeq: add functions to compare files content
Signed-off-by: Karel Zak <kzak@redhat.com>
2021-10-29 13:37:36 +02:00
.github/workflows github: add meson build target 2021-09-16 13:25:07 +02:00
Documentation Fix misspellings 2021-09-04 11:11:04 -03:00
bash-completion su: (bash-completion) offer usernames rather than files 2021-08-31 12:51:40 +02:00
config build-sys: gtkdoc-fixxref v1.27 requires module option 2018-02-01 13:23:40 +01:00
disk-utils mkswap: support -U {clear,random,time,uuid} 2021-09-23 11:53:26 +02:00
include include/fileeq: add functions to compare files content 2021-10-29 13:37:36 +02:00
lib include/fileeq: add functions to compare files content 2021-10-29 13:37:36 +02:00
libblkid Fix misspellings 2021-09-04 11:11:04 -03:00
libfdisk libfdisk: check calloc() return [gcc-analyzer] 2021-08-18 11:35:07 +02:00
libmount test_mount_optstr: use xstrdup() 2021-09-23 13:11:16 +02:00
libsmartcols meson: fix building libsmartcols 2021-09-07 18:58:32 -04:00
libuuid Man pages: Fix end extend formatting 2021-09-21 20:48:11 +02:00
login-utils su: reset also RLIMIT_FSIZE and RLIMIT_NOFILE 2021-10-04 15:39:40 +02:00
m4 build-sys: use $LIBS rather than LDFLAGS 2021-06-18 17:21:13 +02:00
man-common fix whitespace issue in ducumentation 2021-05-10 15:53:50 +02:00
misc-utils hardlink: improve verbose messages 2021-10-07 13:11:18 +02:00
po Fix typo 2021-07-22 19:03:54 +03:00
po-man build-sys: fix po-man/ make check 2021-05-13 12:21:56 +02:00
schedutils uclampset: Fix left over optind++ 2021-06-08 15:56:00 +02:00
sys-utils mount.8.adoc: note that mandatory locking is fully deprecated in Linux 5.15 2021-10-04 12:17:51 +02:00
term-utils setterm: (man) improve dosc about optional arguments 2021-09-27 12:49:01 +02:00
tests tests: use subtests 2021-09-13 10:59:59 +02:00
text-utils more: fix -e in non-interactive mode 2021-10-05 10:53:13 +02:00
tools tools/git-version-gen: use NEWS as a fallback 2021-07-14 15:57:00 +02:00
.editorconfig add .editorconfig 2016-01-25 00:12:14 +01:00
.gitignore build-sys: add .stamp to gitignore 2021-04-23 10:39:35 +02:00
.travis-functions.sh travis: cleanup before autogen 2021-04-09 08:02:10 +02:00
.travis.yml travis: remove old ubuntu 2021-01-26 15:25:54 +01:00
AUTHORS docs: add uclampset to AUTHORS file 2021-06-01 10:32:35 +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: make re-use of generated man-pages more robust 2021-06-04 11:46:55 +02:00
NEWS build-sys: release++ (v2.37) 2021-06-01 09:52:10 +02:00
README docs: add hint about make install-strip and link to Documentation/ 2020-10-06 15:35:09 +02:00
README.licensing docs: add GPLv3 text 2019-11-08 11:10:54 +01:00
autogen.sh build-sys: make autogen.sh output more user friendly 2021-06-09 16:09:16 +02:00
configure.ac hardlink: remove pcre2posix.h support 2021-07-14 17:51:07 +02:00
meson.build meson: fix typo 2021-09-24 15:52:07 +02:00
meson_options.txt meson: make raw(7) optional 2021-09-23 14:09:35 +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".


      See Documentation/howto-compilation.txt.


      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:

 See also:

 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.