Update MaintNotes in preparation for 1.5.4
Junio C Hamano committed
Feb 1, 2008 at 19:56 UTC
eb4be62ca56613d9cb8b7d99c4571ff2b91693ff
2 files changed
+3
-2
MaintNotes
+2
-2
@@ -91,7 +91,7 @@ but they are not expected to be anything major, and more
91
importantly quickly and trivially fixable. Every now and
92
then, a "feature release" is cut from the tip of this branch and
93
they typically are named with three dotted decimal digits. The
94
-last such release was v1.5.3 done on Sep 2nd last year. You
94
+last such release was v1.5.4 done on Feb 2nd this year. You
95
can expect that the tip of the "master" branch is always more
96
stable than any of the released versions.
97
@@ -100,7 +100,7 @@ from "master" at that point. Obvious, safe and urgent fixes
100
after a feature release are applied to this branch and
101
maintenance releases are cut from it. The maintenance releases
102
are named with four dotted decimal, named after the feature
103
-release they are updates to; the last such release was v1.5.3.7.
103
+release they are updates to; the last such release was v1.5.3.8.
104
New features never go to this branch. This branch is also
105
merged into "master" to propagate the fixes forward.
106
SE
+1
@@ -28,6 +28,7 @@ git send-email \
28
--from="$me" \
29
--envelope-sender="$me" \
30
--to="$to" \
31
+ --no-signed-off-cc \
32
--suppress-from \
33
--smtp-server=$smtp \
34
$dryrun \