aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorGravatar Carl Worth <cworth@cworth.org>2010-11-01 16:16:03 -0700
committerGravatar Carl Worth <cworth@cworth.org>2010-11-01 16:16:03 -0700
commitefee51ba756a589998c1894f6574ebe8a6e280d4 (patch)
treed7e5780481093ba1d15ad8150ec9f54c2d5d6f07
parent4dd066ae6cef50eeed805ab16c10a2190de606fb (diff)
Increment notmuch version to 0.4.
As reminded in the RELEASING instructions, the correct version is 0.4, not 0.4.0, so update this in the NEWS file as well.
-rw-r--r--NEWS4
-rw-r--r--RELEASING8
-rw-r--r--version2
3 files changed, 7 insertions, 7 deletions
diff --git a/NEWS b/NEWS
index 92abb3db..db437d31 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,5 @@
-Notmuch 0.4.0 (2010-11-01)
-==========================
+Notmuch 0.4 (2010-11-01)
+========================
New command-line features
-------------------------
notmuch search --output=(summary|threads|messages|tags|files)
diff --git a/RELEASING b/RELEASING
index e9cb3d0b..6c714f8e 100644
--- a/RELEASING
+++ b/RELEASING
@@ -48,10 +48,10 @@ repository. From here, there are just a few steps to release:
as "1.1" or "1.2").
Finally, releases that do not change "features" but are merely
- bug fixes either add increase the micro number or add it
- (starting at ".1" if not present). So a bug-fix release from
- "1.0" would be "1.0.1" and a subsequent bug-fix release would
- be "1.0.2" etc.
+ bug fixes either increase the micro number or add it (starting
+ at ".1" if not present). So a bug-fix release from "1.0" would
+ be "1.0.1" and a subsequent bug-fix release would be "1.0.2"
+ etc.
Commit this change.
diff --git a/version b/version
index 9e11b32f..bd73f470 100644
--- a/version
+++ b/version
@@ -1 +1 @@
-0.3.1
+0.4