2 Bcc: mailx-announce-bcc
3 # NOT YET, should be left alone for that! Mail-Followup-To: mailx
8 hereby i announce S-nail vXX.X.X, the «».
18 The tagged release commits are [master stable/v]:[], and
19 [release/v]:[] (actual release content).
20 The release has also been stored as [timeline]:[].
21 The git(1) release commits and tags as well as the release tarball
22 itself have been signed with the OpenPGP key
23 steffen@sdaoden.eu / 95F382CE
24 (232C 220B CB56 90A3 7BD2 2FFD EB66 0227 95F3 82CE)
25 available on OpenPGP key servers, my website and download area,
26 and also in the repository (blob tagged steffen-pgp-pub).
28 Release tarballs and signatures (.asc) can be downloaded via
29 HTTPS/HTTP and anonymous active or passive FTPS/FTP (in fact still
30 www.sdaoden.eu/downloads, but only via HTTPS/HTTP):
32 \https?://ftp.sdaoden.eu
33 \ftps?://ftp.sdaoden.eu
35 s-nail-XX.X.X.tar.xz{,.asc}:
39 -----BEGIN PGP SIGNATURE-----
40 -----END PGP SIGNATURE-----
42 s-nail-XX.XX.XX.tar.gz{,.asc}:
46 -----BEGIN PGP SIGNATURE-----
47 -----END PGP SIGNATURE-----
49 All files are available as "-latest" symbolic links, too, e.g.,
50 s-nail-latest.txt (a copy of this announcement text).
52 Announcement : https?://www.sdaoden.eu/code-nail-ann.html
53 Manual : https?://www.sdaoden.eu/code-nail.html
54 Web : https?://www.sdaoden.eu/code.html#s-mailx
55 git(1) clone : \https?://git.sdaoden.eu/scm/s-nail.git
56 git(1) browse: https?://git.sdaoden.eu/cgit/s-nail.git
58 In the following mdocmx(7) anchors are denoted by a number-sign #:
59 typing "^A ANCHOR" while reading the man(1)ual in a capable less(1)
60 will scroll to the manual's Point-Of-Interest, and pointing a web-
61 browser to the "#ANCHOR" of the online manual will do so, too.
63 NOTES, ChangeLog (packager-affine)
64 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
66 - .tar files are no longer provided, and i have removed all old cruft
67 from the download area.
72 git(1) shortlog (edited)
73 ^^^^^^^^^^^^^^^^^^^^^^^^
75 :read!git shortlog -w78,0,8 --format="\%h \%s" x..y
81 The complete changelog of commits in between two versions OLD and
82 NEW can be inspected by using the git(1) `log' command:
84 $ git log --reverse --topo-order --abbrev-commit OLD..NEW
85 # Only topic branch headers (--no-merges for content commits only):
86 $ git log --oneline --reverse --topo-order --merges OLD..NEW
87 # Same, but truly accessible:
88 $ git log --oneline --reverse --topo-order --merges --parents OLD..NEW |
89 while read c1 c2 c3 c4 c5 c6; do
90 printf "%-24s: \$ git log --oneline --no-merges %s ^%s\n" \
91 "${c6}" "${c1}" "${c2}";
94 The vXX.X.* announcements have been shortened at this point;
95 to see the elder entries please have a look at [1].
97 [1] https://www.mail-archive.com/s-nail-users@lists.sourceforge.net/msgXXXXX.html
99 Even elder announcements:
100 v14.8.0 - v14.8.6: 00292
101 v14.8.7 - v14.8.8: 00374, v14.8.9: 00435, v14.8.10: 00445
102 [v14.8.11: 00495], v14.8.12: 00502, [v14.8.13: 00514], v14.8.14: 00519
104 v14.7.1: 00129, v14.7.2 - v14.7.8: 00193, v14.7.9 - v14.7.10: 00216,
106 Replace the XXX in the following URL with the shown number:
107 \https://www.mail-archive.com/s-nail-users@lists.sourceforge.net/msgXXX.html