4 util-linux is a random collection of Linux utilities
6 Note: for the years 2006-2010 this project was named "util-linux-ng".
10 See Documentation/howto-compilation.txt.
14 E-MAIL: util-linux@vger.kernel.org
15 URL: http://vger.kernel.org/vger-lists.html#util-linux
16 ARCHIVE: https://lore.kernel.org/util-linux/
18 The mailing list will reject email messages that contain:
19 - more than 100K characters
21 - spam phrases/keywords
22 See: http://vger.kernel.org/majordomo-info.html#taboo
26 #util-linux at libera.chat:
28 irc://irc.libera.chat/util-linux
30 The IRC channel and Mailing list are for developers and project
31 maintainers. For end users it is recommended to utilize the
32 distribution's support system.
36 E-MAIL: util-linux@vger.kernel.org
37 Web: https://github.com/util-linux/util-linux/issues
39 Bug reports with sensitive or private information: Karel Zak <kzak@redhat.com>
41 This project has no resources to provide support for distribution specific
42 issues. For end users it is recommended to utilize the distribution's
45 NLS (PO TRANSLATIONS):
47 PO files are maintained by:
48 http://translationproject.org/domain/util-linux.html
53 <major>.<minor>[.<maint>]
54 major = fatal and deep changes
55 minor = typical release with new features
56 maint = maintenance releases; bug fixes only
64 https://www.kernel.org/pub/linux/utils/util-linux/
67 Documentation/howto-contribute.txt
68 Documentation/howto-build-sys.txt
69 Documentation/howto-pull-request.txt
71 SCM (Source Code Management) Repository:
74 git clone git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git
77 git clone git://github.com/util-linux/util-linux.git
80 http://git.kernel.org/cgit/utils/util-linux/util-linux.git
81 https://github.com/util-linux/util-linux
83 Note: the GitHub repository may contain temporary development branches too.
85 The kernel.org repository contains master (current development) and stable/*
86 (maintenance) branches only. All master or stable/* changes are always pushed
87 to both repositories at the same time.
89 Repository Branches: 'git branch -a'
92 - the source for stable releases when deemed ready.
93 - day-to-day status is: 'it works for me'. This means that its
94 normal state is useful but not well tested.
95 - long-term development or invasive changes in active development are
96 forked into separate 'topic' branches from the tip of 'master'.
100 - branch name: stable/v<major>.<minor>.
101 - created from the 'master' branch after two or more release
102 candidates and the final public release. This means that the stable
103 releases are committed, tagged, and reachable in 'master'.
104 - these branches then become forked development branches. This means
105 that any changes made to them diverge from the 'master' branch.
106 - maintenance releases are part of, and belong to, their respective
107 stable branch. As such, they are tags(<major>.<minor>.<maint>) and
108 not branches of their own. They are not part of, visible in, or
109 have anything to do with the 'master' development branch. In git
110 terminology: maintenance releases are not reachable from 'master'.
111 - when initially cloned (as with the 'git clone' command given above)
112 these branches are created as 'remote tracking branches' and are
113 only visible by using the -a or -r options to 'git branch'. To
114 create a local branch use the desired tag with this command:
115 'git checkout -b v2.29.2 v2.29.2'
118 - a new tag object is created for every release.
119 - tag name: v<version>.
120 - all tags are signed by the maintainer's PGP key.
123 - don't use tag v2.13.1 (created and published by mistake),
124 use v2.13.1-REAL instead.
128 1) development (branch: <master>)
130 2) master release (tags: v2.29-rc1, v2.29-rc2, v2.29, branch: <master>)
132 3) development (work on v2.30, branch: <master>)
134 4) fork -- create a new branch <stable/v2.29> based on tag v2.29
136 4a) new patches or cherry-pick patches from <master> (branch: <stable/v2.29>)
138 4b) stable release (tag: v2.29.1, branch: <stable/v2.29>)
140 4c) more patches; another release (tag: v2.29.2, branch: <stable/v2.29>)
142 5) master release v2.30 (branch: <master>)
145 where 3) and 4) happen simultaneously.