| Commit message (Collapse) | Author | Age |
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
NEWS
Conflicts resolved by inserting the 0.10.2 stanza before 0.11
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This optimizes the user's tagging query to exclude messages that won't
be affected by the tagging operation, saving computation and IO for
redundant tagging operations.
For example,
notmuch tag +notmuch to:notmuch@notmuchmail.org
will now use the query
( to:notmuch@notmuchmail.org ) and (not tag:"notmuch")
In the past, we've often suggested that people do this exact
transformation by hand for slow tagging operations. This makes that
unnecessary.
|
|
|
|
|
| |
Explain the bug fix in slightly less technical language than in the
Debian changelog.
|
|
|
|
| |
It doesn't really matter if we are off by a day.
|
|
|
|
|
| |
This is maybe borderline for inclusion in NEWS, but maybe the NEWS
item helps someone who thinks there is a bug.
|
|
|
|
| |
(with a further M-x whitespace-cleanup by db)
|
|
|
|
|
|
| |
Add news entries for commits:
f9764bfacc97457d1154c2d2a6001a6564f13ec3
64febdf71c4184ca369f5d11d7f196704a3ec1a6
|
|
|
|
|
|
| |
This adds a NEWS entry for commit 4a4ada73b751b1916c5dc4d408a8056411566e38
(second try, with whitespace fix)
|
|
|
|
|
|
| |
This reverts commit e93bf1f842d4d06b2468d1cdbd5e4e25877c7a44.
reverting to fix whitespace
|
|
|
|
| |
This adds a NEWS entry for commit 4a4ada73b751b1916c5dc4d408a8056411566e38
|
|
|
|
| |
Add a news entry for commit6a280088e6769015ade7758b9790384997a21ff3.
|
|
|
|
|
|
| |
Performance
via email: id:"20111116154317.GC2852@mit.edu"
|
|
|
|
|
| |
I mention the possibility of a seperate license here because currently
notmuch-deliver is licensed GPL v2 only.
|
|
|
|
|
|
|
| |
Add support for --output=messages (which remains the default) and
--output=threads to notmuch count.
Signed-off-by: Jani Nikula <jani@nikula.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add options --offset=[-]N and --limit=M to notmuch search to determine the
first result and maximum number of results to display.
Option --limit=M limits the maximum number of results to display to M.
Option --offset=[-]N skips the first N results; with the leading '-' skip
until the Nth result from the end.
Note that --offset with a negative N for thread or summary output requires
counting the number of matching threads in advance.
Signed-off-by: Jani Nikula <jani@nikula.org>
|
| |
|
|
|
|
| |
This brings NEWS back in line with the actual code.
|
|
|
|
|
|
| |
Hopefully this will be fixed before release, but for the moment,
explain to people why their test suite might not be working like it
used to.
|
|
|
|
|
|
| |
As a side effect, reformat the NEWs entry for notmuch dump for
consistency with the notmuch restore NEWS submitted by Thomas
Schwinge.
|
|
|
|
|
| |
We mention in all three places that using the filename argument is
deprecated.
|
|
|
|
|
| |
For details the user will have to refer to the source. Reformat Ruby
news consistently with Python.
|
|
|
|
| |
For details the user will have to refer to the source.
|
| |
|
|
|
|
|
|
|
|
| |
Make note that find_message_by_name currently crashes the python process
if the Database is READ-ONLY. This should be fixed in the underlying
libnotmuch.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
|
|
|
|
|
|
| |
List major changes.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
|
|
|
|
| |
Just the one unicode related change this release.
|
|
|
|
| |
This is based on a quick scan of git log.
|
|
|
|
|
| |
Thanks to Austin Clements for providing these notes, and the patches
they describe.
|
| |
|
| |
|
| |
|
|
|
|
| |
Sed was POSIXed and use of nm dumbed down, replaced by awk hackery.
|
| |
|
|
|
|
| |
Essentially point form from git log --oneline.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fix some typos, add some notes on python bindings, "improve" the folder searching
description, expand the discussion of crypto changes.
This includes the changes from
id:"1309541202-4938-1-git-send-email-dmitry.kurochkin@gmail.com"
Thanks to Sebastian, Austin, and Uwe, Dmitry for the editing help.
|
|
|
|
|
|
| |
By skimming through "git log 0.5..origin/release" late at
night. Hopefully everything here is accurate.
(cherry picked from commit d173069ad9cf042458f16af00729867cb13bb3b7)
|
|
|
|
| |
Which is ready to go now.
|
|
|
|
| |
These two changes since the 0.4 release are noteworthy.
|
|
|
|
|
| |
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.
|
|
|
|
| |
Which is about to be pushed out.
|
|
|
|
| |
I'm trying to get into the habit of maintaining the NEWS file as I go.
|
|
|
|
|
|
|
|
|
| |
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>
|
|\
| |
| |
| |
| | |
This brings one bug fix into master that was originally applied
directly to the 0.3.x branch.
|
| |
| |
| |
| |
| |
| |
| | |
"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).
|
| |
| |
| |
| | |
Signed-off-by: Dirk Hohndel <hohndel@infradead.org>
|
|\|
| |
| |
| |
| |
| |
| |
| | |
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).
|
| |
| |
| |
| |
| | |
This is going to be a bug-fix only release to fix the handful of issue
noticed immediately after 0.3 was pushed out.
|
| |
| |
| |
| |
| |
| | |
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.
|