| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
Unfortunately release-checks.sh will whine a bit because it has not
caught up with the renaming of the version macros.
|
|
|
|
|
|
|
|
| |
Roll (one last?) release candidate because of Austin's
LIBNOTMUCH_VERSION changes.
Atomically bump the manually (NEWS, debian/changelog) and
automatically (everywhere else) updated places version is mentioned.
|
| |
|
|
|
|
|
| |
Various other files are synched using "make update-versions". NEWS
has to be hand edited.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, reply's default text format used an odd mix of RFC 2045
MIME encoding for the reply template's body and some made-up RFC
2822-like UTF-8 format for the headers. The intent was to present the
headers to the user in a nice, un-encoded format, but this assumed
that whatever ultimately sent the email would RFC 2047-encode the
headers, while at the same time the body was already RFC 2045 encoded,
so it assumed that whatever sent the email would *not* re-encode the
body.
This can be fixed by either producing a fully decoded UTF-8 reply
template, or a fully encoded MIME-compliant RFC 2822 message. This
patch does the latter because it is
a) Well-defined by RFC 2822 and MIME (while any UTF-8 format would be
ad hoc).
b) Ready to be piped to sendmail. The point of the text format is to
be minimal, so a user should be able to pop up the template in
whatever editor they want, edit it, and push it to sendmail.
c) Consistent with frontend capabilities. If a frontend has the
smarts to RFC 2047 encode the headers before sending the mail, it
probably has the smarts to RFC 2047 decode them before presenting
the template to a user for editing.
Also, as far as I know, nothing automated consumes the reply text
format, so changing this should not cause serious problems. (And if
anything does still consume this format, it probably gets these
encoding issues wrong anyway.)
|
|
|
|
|
| |
man pages, NEWS, and debian changelog all hardcode date. Make them
hardcode the same date.
|
|
|
|
|
| |
These are manually set in version and NEWS, and propagate to the other files via
"make update-versions"
|
|
|
|
| |
Add references to notmuch-insert.1 from other man pages.
|
| |
|
| |
|
|
|
|
| |
A simple bugfix release, no user visible changes
|
|
|
|
| |
Bump the version in-place in NEWS.
|
|
|
|
|
| |
This is in some sense a rollback, but it makes all the automation
happier if the Debian and upstream versions match.
|
|
|
|
| |
"Atomically" update the python bindings and man page versions.
|
| |
|
|
|
|
|
| |
Add sections about the new S-Expression output format (--format=sexp) to
the notmuch-search, notmuch-reply and notmuch-show man pages.
|
|
|
|
| |
These are the result of running "make update-versions"
|
|
|
|
|
|
| |
The NAME section in manpages generally doesn't start with capital
letter (unless the word is 'proper noun') and doesn't end with
period. Notmuch manual pages now matches that "format".
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
NEWS
Conflicts resolved by hand for date of 0.12 release.
|
| |
| |
| |
| | |
There may be a few NEWS changes after this, but no code (hopefully).
|
| | |
|
|/ |
|
| |
|
|
|
|
|
| |
Drop references to notmuch-part(1). Reference all man pages. Fix man
page section of notmuch-dump(1).
|
|
|
|
|
| |
As usual, only `version' is edited by hand. The rest of the changes I
blame on the machine.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add new option --reply-to=(all|sender) to "notmuch reply" to select whether
to reply to all (sender and all recipients), or just sender. Reply to all
remains the default.
Credits to Mark Walters <markwalters1009@gmail.com> for his similar earlier
work where I picked up the basic idea of handling reply-to-sender in
add_recipients_from_message(). All bugs are mine, though.
Signed-off-by: Jani Nikula <jani@nikula.org>
|
|
|
|
| |
Signed-off-by: Jani Nikula <jani@nikula.org>
|
|
|
|
|
|
|
| |
- Replace references to section X below with page refences.
- Add SEE ALSO to each page. This is a bit error prone, because each
SEE ALSO section is different, i.e. a page does not refer to itself.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix some problems with indentation (controlled by markup) and
whitespace.
- notmuch.1: reformat
Use .SS macro to make "notmuch setup" a subsection. Introduce another
subsection for the remaining commands.
- notmuch-config.1: reformat
Put all the syntax in the synopsis. Supposedly this is the the UNIX way.
- notmuch-reply.1: fix formatting issues.
Give nicer formatting for synopsis.
Insert missing SEE ALSO header.
- notmuch-dump.1: reformat using subsections
These seems more natural, although, as mentioned, it does require
referring back to the synopsis. Or maybe copying parts of the
synopsis
|
|
We mostly just cut and paste the command descriptions into individual
files, with a short header added to each one.
The splitting into subdirectories is to support the use of ./man as an
element in MANPATH, e.g. for testing.
|