Go to file
Karel Zak 670b10ae36 lib/c_strtod; add locale independent strtod()
Signed-off-by: Karel Zak <kzak@redhat.com>
2021-05-25 11:31:08 +02:00
.github/workflows github: fix asciidoctror dependence 2021-03-29 18:56:12 +02:00
Documentation lscpu: add SCALMHZ% and "CPU scaling MHz:" 2021-05-24 13:39:53 +02:00
bash-completion bash-completion: (lsblk) fix -E/-M arg (non-)completion 2021-04-16 22:08:48 +03:00
config build-sys: gtkdoc-fixxref v1.27 requires module option 2018-02-01 13:23:40 +01:00
disk-utils mkswap: remove unused variable when compile without libblkid 2021-05-07 20:37:51 +02:00
include lib/c_strtod; add locale independent strtod() 2021-05-25 11:31:08 +02:00
lib lib/c_strtod; add locale independent strtod() 2021-05-25 11:31:08 +02:00
libblkid libblkid: support zone reset for wipefs 2021-05-24 13:39:53 +02:00
libfdisk libfdisk: (script) print bootable flag only when set 2021-05-06 17:01:48 +02:00
libmount libmount: fix memory leak [coverity scan] 2021-03-25 11:03:03 +01:00
libsmartcols lib/jsonwrt: remove 'islast' from API 2021-05-06 15:58:02 +02:00
libuuid test_uuid_parser: fix time_t=long assumptions 2021-05-06 10:43:13 +02:00
login-utils sulogin: fix whitespace error 2021-05-24 13:39:53 +02:00
m4 build-sys: add UL_REQUIRES_PROGRAM() macro, use it for asciidoc 2021-04-07 10:19:03 +02:00
man-common fix whitespace issue in ducumentation 2021-05-10 15:53:50 +02:00
misc-utils fix whitespace issue in ducumentation 2021-05-10 15:53:50 +02:00
po po: merge changes 2021-05-10 12:21:25 +02:00
po-man build-sys: fix po-man/ make check 2021-05-13 12:21:56 +02:00
schedutils build-sys: keep adoc files in dist_noinst_DATA 2021-05-05 13:35:30 +02:00
sys-utils lscpu: use MHZ as number to be locale sensitive 2021-05-24 13:39:53 +02:00
term-utils fix whitespace issue in ducumentation 2021-05-10 15:53:50 +02:00
tests tests: update lscpu output 2021-05-24 13:43:02 +02:00
text-utils more: fix floating point exception core dump 2021-05-19 20:23:48 +01:00
tools tools: add missing stuff to Makefile.am 2021-04-09 07:53:21 +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: update AUTHORS file 2021-05-10 13:09:13 +02:00
ChangeLog docs: Correct ChangeLog URL to history log. 2020-05-11 09:48:43 +02:00
Makefile.am build-sys: keep adoc files in dist_noinst_DATA 2021-05-05 13:35:30 +02:00
NEWS build-sys: release++ (v2.37-rc2) 2021-05-10 13:12:02 +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: improve bison version detection 2018-04-30 09:43:32 +02:00
configure.ac lib/c_strtod; add locale independent strtod() 2021-05-25 11:31:08 +02:00
meson.build lib/c_strtod; add locale independent strtod() 2021-05-25 11:31:08 +02:00
meson_options.txt meson: add irq utils 2021-03-25 12:12:11 +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".


      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.