Go to file
Karel Zak 3bd55be742 lib/sha1: use ul_/UL_prefix for symbols
Unfortunately, the symbols are visible in statically compiled libuuid
and the names are too generic.

Addresses: https://github.com/karelzak/util-linux/issues/548
Signed-off-by: Karel Zak <kzak@redhat.com>
2017-12-12 11:29:02 +01:00
Documentation docs: update TODO file 2017-11-23 15:02:32 +01:00
bash-completion bash-completion: (umount) use findmnt, escape a space in paths 2017-11-16 16:27:32 +01:00
config build-sys: inform gtk-doc about __ul_attribute__ 2013-03-15 14:58:08 +01:00
disk-utils blockdev: be more explicit for BLKSSZ in blockdev.8 2017-11-13 12:15:17 +01:00
include lib/sha1: use ul_/UL_prefix for symbols 2017-12-12 11:29:02 +01:00
lib lib/sha1: use ul_/UL_prefix for symbols 2017-12-12 11:29:02 +01:00
libblkid libblkid: add debug messages when ignore useless devices 2017-12-07 12:15:48 +01:00
libfdisk misc: fix typos 2017-11-28 14:39:13 +01:00
libmount libmount: add nsfs between pseudo filesystems 2017-11-21 12:11:56 +01:00
libsmartcols misc: fix typos 2017-11-28 14:39:13 +01:00
libuuid lib/sha1: use ul_/UL_prefix for symbols 2017-12-12 11:29:02 +01:00
login-utils vipw: do not let editor to inherit open file descriptors 2017-12-04 13:04:11 +01:00
m4 build-sys: add libtinfow check 2017-09-19 12:55:49 +02:00
misc-utils rename: use access(3) to check if a file exists 2017-12-04 13:04:12 +01:00
po po: merge changes 2017-10-19 12:57:57 +02:00
schedutils misc: consolidate macro style USAGE_HELP_OPTIONS 2017-06-29 16:54:33 +02:00
sys-utils Merge branch '2017wk48' of https://github.com/kerolasa/lelux-utiliteetit 2017-12-11 16:03:39 +01:00
term-utils agetty: Fix a use of uninitialised memory in an agetty error path. 2017-11-21 10:54:39 +01:00
tests tests: unlocks on failed ts_scsi_debug_init 2017-12-07 15:08:29 +01:00
text-utils misc: fix typos 2017-11-28 14:39:13 +01:00
tools tools: add segfault detection for checkusage.sh 2017-06-29 14:04:29 +02:00
.editorconfig add .editorconfig 2016-01-25 00:12:14 +01:00
.gitignore rfkill: make command to build in util-linux project 2017-08-30 20:32:48 +01:00
.travis-functions.sh travis: add make checkusage 2017-06-27 08:25:30 +02:00
.travis.yml travis: minor cosmetics 2017-06-15 09:13:14 +02:00
AUTHORS docs: update AUTHORS file 2017-10-19 13:00:06 +02:00
COPYING docs: corrections to FSF license files, and postal address 2012-02-24 14:13:35 +01:00
ChangeLog build-sys: use AUTOMAKE_OPTIONS = gnu 2011-05-26 15:04:01 +02:00
Makefile.am build: use --runstatedir instead of --localstatedir 2017-07-31 15:24:46 +02:00
NEWS build-sys: release++ (v2.31) 2017-10-19 13:08:49 +02:00
README docs: add information about mailing list rejection 2017-06-01 19:42:21 -04:00
README.licensing COPYING: fix grammar of referring phrase, and indicate location better 2013-10-08 15:38:39 +02:00
autogen.sh build-sys: add parse-date.y 2017-03-04 11:01:56 -05:00
configure.ac build-sys: lsns requires libmount 2017-11-27 17:44:43 +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

      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.