From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] limit option parser nil check
Date: Mon, 18 May 2009 11:26:10 -0700 [thread overview]
Message-ID: <1242671123-sup-6919@entry> (raw)
In-Reply-To: <1242205071-sup-2484@tomsk>
Reformatted excerpts from Marcus Williams's message of 2009-05-13:
> The limit search option doesnt check if the current search term is nil
> (when chronic has failed for instance). This patch (against next) adds
> the check.
I've reworked this code in the parser-user-query-fix branch, currently
merged into next, and it should no longer require this fix.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-05-18 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 9:00 Marcus Williams
2009-05-18 18:26 ` William Morgan [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1242671123-sup-6919@entry \
--to=wmorgan-sup@masanjin.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox