public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Tony Parent" <tony.parent@lsil.com>
To: Bob Manson <bmanson@juniper.net>
Cc: Rick Macdonald <rickm@vsl.com>,
	gnats-devel@sourceware.cygnus.com, bug-gnats@gnu.org
Subject: Re: gnatsd accepting new PRs
Date: Mon, 23 Aug 1999 11:28:00 -0000	[thread overview]
Message-ID: <14273.37087.510501.649059@merlin.co.lsil.com> (raw)
In-Reply-To: <199908231803.LAA09975@tristam.juniper.net>

On August 23, 1999, Bob Manson wrote:
> In message < Pine.GSO.4.10.9908231147140.20253-100000@sys4 >, Rick Macdonald writ
> es:
> >I don't suppose that this ever got picked up? The patch probably wouldn't
> >match your new code now.
> 
> It's certainly not in the source tree I've been working with, but I
> suspect it can be made to work without too much trouble.  It may be even
> easier now, I don't know.  (At least it *should* be easy to implement, so
> if it's not that needs to be fixed.)
> 
> Nothing in the "backend" code calls punt, or I should say "should call
> punt" so if that was the fundamental problem that's long since been
> addressed.
> 						Bob

As I remember it, the problem was that the code in file-pr.c called punt
(for things like missing fields etc), but punt calls exit. (So if a
required field was missing, the PR wasn't created.) I had to modify
the punt code so it wouldn't exit the server if file-pr had an error, but
simply return to the main loop of the server.

It's probably good that you haven't seen my code, or you would had more
"crap code" to delete. :-)

-- 
===========================================================================
     oO   Tony.Parent@lsil.com      LSI Logic                         __o
    []<                             2001 Danfield Ct                 -\<,
      |   (970) 206-5769            Fort Collins, CO 80525          O / O
===========================================================================

      reply	other threads:[~1999-08-23 11:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-18 11:21 proclamation of intent Bob Manson
1999-08-18 12:36 ` Rick Macdonald
1999-08-18 13:13   ` Bob Manson
1999-08-18 13:37     ` Stephen Dahmen
1999-08-18 14:15     ` Rick Macdonald
1999-08-23 10:21     ` Rick Macdonald
1999-08-23 10:27       ` Paul Traina
1999-08-23 10:28         ` Rick Macdonald
1999-08-24  5:23         ` Mike Sutton
1999-08-24  9:56           ` Michael Richardson
1999-08-23 10:38       ` Bob Manson
1999-08-23 10:48         ` Paul Traina
1999-08-23 10:52           ` Bob Manson
1999-08-23 10:54             ` Paul Traina
1999-08-23 11:13           ` Rick Macdonald
1999-08-23 11:32             ` Tony Parent
1999-08-23 11:41               ` Rick Macdonald
1999-08-23 12:12             ` Bob Manson
1999-08-23 15:54               ` client info format ideas Rick Macdonald
1999-08-24  5:35             ` proclamation of intent Mike Sutton
1999-08-23 10:58         ` gnatsd accepting new PRs Rick Macdonald
1999-08-23 11:03           ` Bob Manson
1999-08-23 11:28             ` Tony Parent [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=14273.37087.510501.649059@merlin.co.lsil.com \
    --to=tony.parent@lsil.com \
    --cc=bmanson@juniper.net \
    --cc=bug-gnats@gnu.org \
    --cc=gnats-devel@sourceware.cygnus.com \
    --cc=rickm@vsl.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).