public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: overseers@sources.redhat.com
Subject: Re: Just use google for archive searching?
Date: Sat, 21 Dec 2002 21:29:00 -0000	[thread overview]
Message-ID: <87znqyx56q.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <20021220024950.GA9178@redhat.com> (Christopher Faylor's message of "Thu, 19 Dec 2002 21:49:50 -0500")

Christopher Faylor <cgf@redhat.com> writes:

> It seems like we might be able to just stop doing htdig and let google
> do our archiving for us.

I have thought of a technical reason why this is not a good idea.

When I do site searches, it's always the mailing lists I'm searching,
it's almost always for an exact string, and I want to see the results
sorted by date.  Google doesn't provide a convenient way to limit the
search to just the mailing lists, nor to sort the results by date, and
I'm not sure what their rules are regarding characters that can appear
in strings.  (The search I want boils down to recursive 'grep' --
regular expressions and all -- which htdig doesn't give me either, of
course.)

zw

      parent reply	other threads:[~2002-12-22  0:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 21:41 Christopher Faylor
2002-12-19 21:52 ` Hans-Peter Nilsson
2002-12-19 23:46   ` Hans-Peter Nilsson
2002-12-20  2:27     ` Zack Weinberg
2002-12-20 11:50       ` Hans-Peter Nilsson
2002-12-20 12:31         ` Christopher Faylor
2002-12-20 14:15           ` Hans-Peter Nilsson
2002-12-20 21:33             ` Joseph S. Myers
2002-12-21  9:31               ` Jonathan Larmour
2002-12-21 16:21                 ` Joseph S. Myers
2002-12-21 16:34                   ` Jonathan Larmour
2002-12-21 20:21                     ` Joseph S. Myers
2002-12-21  5:11             ` Christopher Faylor
2002-12-21 21:29 ` Zack Weinberg [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=87znqyx56q.fsf@egil.codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=overseers@sources.redhat.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).