Name Date Size

..29-Nov-20194 KiB

.editorconfigH A D17-Aug-2017218

.gitignoreH A D08-Oct-20191.5 KiB

.travis-functions.shH A D16-Dec-20194.8 KiB

.travis.ymlH A D24-Oct-2018836

AUTHORSH A D21-Jan-202032.6 KiB

autogen.shH A D30-Apr-20183.5 KiB

bash-completion/H12-Dec-20194 KiB

ChangeLogH A D17-Aug-201793

config/H01-Feb-20184 KiB

configure.acH A D21-Jan-202075.6 KiB

COPYINGH A D17-Aug-201717.7 KiB

disk-utils/H15-Jan-20204 KiB

Documentation/H03-Jan-20204 KiB

include/H15-Jan-20204 KiB

lib/H13-Jan-20204 KiB

libblkid/H17-Dec-20194 KiB

libfdisk/H16-Aug-20184 KiB

libmount/H05-Dec-20194 KiB

libsmartcols/H16-Aug-20184 KiB

libuuid/H16-Aug-20184 KiB

login-utils/H15-Jan-20204 KiB

m4/H09-Dec-20194 KiB

Makefile.amH A D05-Dec-20197.5 KiB

misc-utils/H07-Jan-20204 KiB

NEWSH A D21-Jan-202073.4 KiB

po/H21-Jan-20204 KiB

READMEH A D17-Dec-20184.4 KiB

README.licensingH A D08-Nov-2019793

schedutils/H17-Dec-20194 KiB

sys-utils/H03-Jan-20204 KiB

term-utils/H21-Jan-20204 KiB

tests/H16-Dec-20194 KiB

text-utils/H17-Dec-20194 KiB

tools/H01-Oct-20194 KiB

util-linux.doapH A D17-Aug-20171.5 KiB

README

1
2				  util-linux
3
4		util-linux is a random collection of Linux utilities
5
6     Note: for the years 2006-2010 this project was named "util-linux-ng".
7
8MAILING LIST:
9
10      E-MAIL:  util-linux@vger.kernel.org
11      URL:     http://vger.kernel.org/vger-lists.html#util-linux
12      ARCHIVE: https://lore.kernel.org/util-linux/
13
14      The mailing list will reject email messages that contain:
15       - more than 100K characters
16       - html
17       - spam phrases/keywords
18      See: http://vger.kernel.org/majordomo-info.html#taboo
19
20IRC CHANNEL:
21
22      #util-linux at freenode.net:
23
24      irc://chat.freenode.net/util-linux
25
26      The IRC channel and Mailing list are for developers and project
27      maintainers. For end users it is recommended to utilize the
28      distribution's support system.
29
30BUG REPORTING:
31
32      E-MAIL: util-linux@vger.kernel.org
33      Web:    https://github.com/karelzak/util-linux/issues
34
35      This project has no resources to provide support for distribution specific
36      issues. For end users it is recommended to utilize the distribution's
37      support system.
38
39NLS (PO TRANSLATIONS):
40
41      PO files are maintained by:
42	  http://translationproject.org/domain/util-linux.html
43
44VERSION SCHEMA:
45
46      Standard releases:
47	  <major>.<minor>[.<maint>]
48	     major = fatal and deep changes
49	     minor = typical release with new features
50	     maint = maintenance releases; bug fixes only
51
52      Development releases:
53	 <major>.<minor>-rc<N>
54
55SOURCE CODE:
56
57 Download archive:
58	  https://www.kernel.org/pub/linux/utils/util-linux/
59
60 SCM (Source Code Management) Repository:
61
62    Primary repository:
63	  git clone git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git
64
65    Backup repository:
66	  git clone git://github.com/karelzak/util-linux.git
67
68    Web interfaces:
69	  http://git.kernel.org/cgit/utils/util-linux/util-linux.git
70	  https://github.com/karelzak/util-linux
71
72      Note: the GitHub repository may contain temporary development branches too.
73
74      The kernel.org repository contains master (current development) and stable/*
75      (maintenance) branches only. All master or stable/* changes are always pushed
76      to both repositories at the same time.
77
78    Repository Branches: 'git branch -a'
79	  master branch
80	   - current development
81	   - the source for stable releases when deemed ready.
82	   - day-to-day status is: 'it works for me'. This means that its
83	     normal state is useful but not well tested.
84	   - long-term development or invasive changes in active development are
85	     forked into separate 'topic' branches from the tip of 'master'.
86
87	  stable/ branches
88	   - public releases
89	   - branch name: stable/v<major>.<minor>.
90	   - created from the 'master' branch after two or more release
91	     candidates and the final public release. This means that the stable
92	     releases are committed, tagged, and reachable in 'master'.
93	   - these branches then become forked development branches. This means
94	     that any changes made to them diverge from the 'master' branch.
95	   - maintenance releases are part of, and belong to, their respective
96	     stable branch. As such, they are tags(<major>.<minor>.<maint>) and
97	     not branches of their own. They are not part of, visible in, or
98	     have anything to do with the 'master' development branch. In git
99	     terminology: maintenance releases are not reachable from 'master'.
100	   - when initially cloned (as with the 'git clone' command given above)
101	     these branches are created as 'remote tracking branches' and are
102	     only visible by using the -a or -r options to 'git branch'. To
103	     create a local branch use the desired tag with this command:
104	     'git checkout -b v2.29.2 v2.29.2'
105
106    Tags: 'git tag'
107	   - a new tag object is created for every release.
108	   - tag name: v<version>.
109	   - all tags are signed by the maintainer's PGP key.
110
111    Known Bugs:
112	- don't use tag v2.13.1 (created and published by mistake),
113	  use v2.13.1-REAL instead.
114
115WORKFLOW EXAMPLE:
116
117 1) development (branch: <master>)
118
119 2) master release (tags: v2.29-rc1, v2.29-rc2, v2.29, branch: <master>)
120
121 3) development (work on v2.30, branch: <master>)
122
123 4) fork -- create a new branch <stable/v2.29> based on tag v2.29
124
125     4a) new patches or cherry-pick patches from <master> (branch: <stable/v2.29>)
126
127     4b) stable release (tag: v2.29.1, branch: <stable/v2.29>)
128
129     4c) more patches; another release (tag: v2.29.2, branch: <stable/v2.29>)
130
131 5) master release v2.30 (branch: <master>)
132    ...
133
134where 3) and 4) happen simultaneously.
135
136

README.licensing

1
2The project util-linux doesn't use the same license for all of the code.
3There is code under:
4
5   * GPL-3.0-or-later   - GNU General Public License version 3, or any later version
6
7   * GPL-2.0-or-later   - GNU General Public License version 2, or any later version
8
9   * GPL-2.0            - GNU General Public License version 2
10
11   * LGPL-2.1-or-later  - GNU Lesser General Public License 2.1 or any later version
12
13   * BSD-3-Clause       - BSD 3-Clause "New" or "Revised" License
14
15   * BSD-4-Clause-UC    - BSD 4-Clause University of California-Specific
16
17   * Public Domain
18
19Please, check the source code for more details. A license is usually at the start
20of each source file.
21
22The ./COPYING file (GPL-2.0-or-later) is the default license for code without
23an explicitly defined license.
24
25