From: "Sebastian Spaeth" <Sebastian@SSpaeth.de>
To: Notmuch development list <notmuch@notmuchmail.org>
Subject: date parser branch updated and rebased
Date: Mon, 08 Feb 2010 10:41:48 +0100 [thread overview]
Message-ID: <87fx5cjc83.fsf@SSpaeth.de> (raw)
In order to not let this bitrot, I just rebased my dateparser branch to
current cworth master and split up the patches in a nicer way.
I made sure that every commit compiles. Let me know if there are things
that should be handled in a different way.
find the git branch here:
http://github.com/spaetz/notmuch-all-feature/commits/dateparser5
All 4 patches are going to be send as a reply to this mail in a second.
Sebastian
next reply other threads:[~2010-02-08 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 9:41 Sebastian Spaeth [this message]
2010-02-08 11:14 ` [PATCH 1/4] add date parser file from Keith Sebastian Spaeth
2010-02-08 11:14 ` [PATCH 2/4] Introduce new notmuch return status NOTMUCH_STATUS_INVALID_DATE Sebastian Spaeth
2010-02-08 11:14 ` [PATCH 3/4] integrate date parser Sebastian Spaeth
2010-02-08 11:14 ` [PATCH 4/4] add documentation for the new daterange parser and remove TODO list item Sebastian Spaeth
2010-02-08 12:57 ` [PATCH] notmuch-test: add tests for counting within absolute time ranges and 'today' Sebastian Spaeth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fx5cjc83.fsf@SSpaeth.de \
--to=sebastian@sspaeth.de \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).