public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Chris Faylor <cgf@redhat.com>, <overseers@sources.redhat.com>
Subject: Re: [bleau@igb.umontreal.ca: Re: OpenGL, -mno-cygwin  ***Aside: mailing list search engine is broken]
Date: Sat, 17 Feb 2001 18:44:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.30.0102172115330.85761-100000@dair.pair.com> (raw)
Message-ID: <20010217184400.yj_HdjSo0OjEbF6KOoMOJx-5h3iKbfJMs6cD5DjkAXk@z> (raw)
In-Reply-To: <877l2pkylq.fsf@creche.redhat.com>

On 17 Feb 2001, Tom Tromey wrote:

> >>>>> "H-P" == Hans-Peter Nilsson <hp@bitrange.com> writes:
>
> H-P> Some such failure.  There were no traces of indexing problems,
> H-P> probably because the sourceware side does not do any automatic
> H-P> checking after indexing.
>
> Is there any way for the indexer itself to detect that it fails and
> then, say, send out email indicating that?  That sure would be nice.

The sourceware side could do like the gcc side does, and invoke htsearch
on the command-line with a little sanity test suite before installing the
updated database.  I've been too paranoid having it send out mail though.
When failing, on the gcc side it just re-indexes from scratch (once), and
moves the log from update-log to update-log.failed, so the last failure is
identifiable and at times traceable.  See htupdate-gcc.sh in infra/bin.

Someone, feel free to copy to sourceware side, or merge the two
htupdate*.sh scripts.  I have been lame^H^H^H^Hcautious in avoiding adding
stuff to the sourceware side, it not being my turf, and me being under the
impression that some responsible sourceware maintainer would come around
and fix it there. ;-)

brgds, H-P

  parent reply	other threads:[~2001-02-17 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-31 19:40 Chris Faylor
2001-02-16 10:19 ` Chris Faylor
2001-12-31 19:40 ` [bleau@igb.umontreal.ca: Re: OpenGL, -mno-cygwin ***Aside:mailing " Hans-Peter Nilsson
2001-02-16 18:02   ` Hans-Peter Nilsson
2001-12-31 19:40   ` [bleau@igb.umontreal.ca: Re: OpenGL, -mno-cygwin ***Aside: mailing " Tom Tromey
2001-02-17  9:19     ` Tom Tromey
2001-12-31 19:40     ` Hans-Peter Nilsson [this message]
2001-02-17 18:44       ` Hans-Peter Nilsson

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=Pine.BSF.4.30.0102172115330.85761-100000@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=cgf@redhat.com \
    --cc=overseers@sources.redhat.com \
    --cc=tromey@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).