notmuch - thread-based email index, search and tagging

	Commit message (Collapse)	Author	Age
*	NEWS: Add notes for 0.5 release.	Carl Worth	2010-11-11
\| \| \| \|	Which is ready to go now.
*	NEWS: Update NEWS files for a couple of recent changes.	Carl Worth	2010-11-06
\| \| \| \|	These two changes since the 0.4 release are noteworthy.
*	Increment notmuch version to 0.4.	Carl Worth	2010-11-01
\| \| \| \| \|	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.
*	NEWS: Add notes for the 0.4.0 release	Carl Worth	2010-11-01
\| \| \| \|	Which is about to be pushed out.
*	NEWS: Document the new "notmuch show --format=mbox" format	Carl Worth	2010-06-08
\| \| \| \|	I'm trying to get into the habit of maintaining the NEWS file as I go.
*	NEWS: describe easier FCC configuration	Sebastian Spaeth	2010-06-03
\| \| \| \| \| \| \| \| \|	I know I should be writing something witty here to make cworth happy, but I can't think for any verbose justification of this patch beyond that submitting a NEWS blurb will make cworth happy too. So let's make him happy. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
*	Merge branch '0.3.x' immediately after the 0.3.1 release	Carl Worth	2010-04-27
\|\ \| \| \| \| \| \| \| \|	This brings one bug fix into master that was originally applied directly to the 0.3.x branch.
\| *	NEWS: Reword the latest bug description slightly.	Carl Worth	2010-04-27
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	"Still needs to be handled correctly" could be misread to suggest that the bug has not actually been fixed yet. So clarify what is actually meant here, (that the bug is unlikely but we're still motivated to fix it).
\| *	Update NEWS to reflect the SEGV bugfix	Dirk Hohndel	2010-04-27
\| \| \| \| \| \| \| \|	Signed-off-by: Dirk Hohndel <hohndel@infradead.org>
* \|	Merge branch '0.3.x'	Carl Worth	2010-04-27
\|\\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This doesn't pull in any code, (everything in 0.3.x was originally cherry-picked from master anyway). But the merge does give us a correct NEWS file showing which fixes are included in 0.3.1 and which features have been commited "since" then, (topologically, not chronologically).
\| *	NEWS: Add notes for the 0.3.1 release	Carl Worth	2010-04-27
\| \| \| \| \| \| \| \| \| \|	This is going to be a bug-fix only release to fix the handful of issue noticed immediately after 0.3 was pushed out.
* \|	NEWS: Note build fix for OpenSolaris (at least).	Carl Worth	2010-04-27
\| \| \| \| \| \| \| \| \| \| \| \|	This hit the list just as I sent out my "final call for 0.3.1 testing" and is just the kind of thing that's nice to get into a maintenance release.
* \|	NEWS: Add notes for the 0.3.1 release	Carl Worth	2010-04-27
\| \| \| \| \| \| \| \| \| \|	I think this is ready to go now, but I'm going to impose a mandatory waiting period this time to catch any last-minute issues.
* \|	Subject: [PATCH] NEWS: add mention of auto-tagging.	Jesse Rosenthal	2010-04-27
\|/ \| \| \|	Describe new auto-tagging functionality in the NEWS.
*	NEWS: Fix spelling errors.	Carl Worth	2010-04-27
\| \| \| \| \|	I ran the spell-checker prior to the last commit, but apparently I hadn't actually saved the buffer.
*	NEWS: Add notes for the 0.3 release.	Carl Worth	2010-04-27
\| \| \| \| \|	Summarizing all the major new features and fixes found in the git log since 0.2. A rather nice list, really.
*	Add NEWS updates for my last batch of patches	Dirk Hohndel	2010-04-26
\| \| \| \| \| \| \|	in the future I'll include those with my patches. Hope it's ok to do this as one single patch for this series. Signed-off-by: Dirk Hohndel <hohndel@infradead.org>
*	Add NEWS section for author reordering	Dirk Hohndel	2010-04-26
\| \| \| \| \| \|	This should be required in all patches Signed-off-by: Dirk Hohndel <hohndel@infradead.org>
*	NEWS: Add release notes for the 0.2 release.	Carl Worth	2010-04-16
\|
*	NEWS: Add some (brief) news items for the initial 0.1 release.	Carl Worth	2010-04-05
	Generally, the NEWS items will describe changes since the previous release. But there's not much we can do for that since we've never had a release before.