public inbox for gnats-cvs@sourceware.org
help / color / mirror / Atom feed
From: bmanson@sourceware.cygnus.com
To: gnats-cvs@sourceware.cygnus.com
Subject: gnats/gnats ChangeLog client.c cmds.c gnatsd.c ...
Date: Mon, 27 Sep 1999 21:49:00 -0000	[thread overview]
Message-ID: <19990928044947.23114.qmail@egcs.cygnus.com> (raw)

CVSROOT:	/cvs/gnats
Module name:	gnats
Changes by:	bmanson@egcs.cygnus.com	99/09/27 21:49:46

Modified files:
	gnats          : ChangeLog client.c cmds.c gnatsd.c pr.h query.c 
	                 query.h 

Log message:
	* pr.h (SearchType): Added DefaultSearchType value.
	
	* query.c (add_query_builtin_field): New function.
	Changed previous callers of add_query_field to use it as
	appropriate.
	(searchTypes): Added entry for DefaultSearchType.
	(pr_match_field): Handle DefaultSearchType.
	
	Boingy boingy boingy.  Can you say "rubber ball on the end of a paddle?"
	
	Comments from query.c:
	
	I don't like having the builtin field stuff either.  However, it
	simplfies query-pr's job, because otherwise it would have to parse
	arguments twice.  The reason is that we don't know the indexes for
	the builtin fields before we've read in and parsed the
	configuration file, and we can't do that until after we've
	processed our arguments to find out if we're a network client (and
	the name of our server etc).
	
	Instead, we refer to the builtin fields directly, and let
	pr_match_field () take care of it later, after we've parsed the
	config file.
	
	We'll probably have to parse arguments twice eventually anyway, but
	let's try to postpone it as long as possible.  One sensible
	alternative is to convert the old-style query options into a
	new-style query expression, then parse that instead.


                 reply	other threads:[~1999-09-27 21:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=19990928044947.23114.qmail@egcs.cygnus.com \
    --to=bmanson@sourceware.cygnus.com \
    --cc=gnats-cvs@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).