From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] searching on subject
Date: Sun, 27 May 2007 20:33:44 -0700 [thread overview]
Message-ID: <1180323050-sup-174@south> (raw)
In-Reply-To: <1179911900-sup-1786@doses>
Excerpts from Brian's message of Wed May 23 02:23:33 -0700 2007:
> /subject:sup-talk
> finds fewer messages than
> /subject:\[sup-talk\]
> even though "sup-talk" is definitely in the subject lines of the
> messages found by the second search.
>
> I thought it was a little unintuitive.
Yeah, this is unnecessarily weird.
I've changed this in SVN. It will take effect immediately for new
messages; to apply it to old messages you'll have to run sup-sync -a
(and wait while every single message is re-indexed).
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-05-28 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 9:23 Brian
2007-05-28 3:33 ` 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=1180323050-sup-174@south \
--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