public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Mel Hatzis <hatzis@juniper.net>
To: Yngve Svendsen <yngve.svendsen@sun.com>
Cc: help-gnats@gnu.org
Cc: "Andrew J. Gray" <andrewg@gnu.org>
Subject: Re: patch to display new PR number for new submissions
Date: Mon, 03 Feb 2003 21:17:00 -0000	[thread overview]
Message-ID: <3E3EDBC2.3060905@juniper.net> (raw)
In-Reply-To: <5.2.0.5.0.20030203214748.0441dc40@ms-etro01-01.norway.sun.com>

On 02/03/2003 12:49 PM, Yngve Svendsen wrote:
> At 12:42 03.02.2003 -0800, Mel Hatzis wrote:
> 
>> I'm in favour of rolling out 4.0 pretty soon....if you think putting
>> this patch on a 4.1 branch would help this endevour, I'd suggest
>> you do just that.
> 
> 
> I agree strongly. I have a few small but potentially high-risk changes 
> for Gnatsweb queued up that I don't want to apply to 4.0, so I'd like 
> version 4.0 of both GNATS and Gnatsweb to be out of the door before I 
> branch for version 4.1 of Gnatsweb.
> 
> Yngve Svendsen
> Gnatsweb maintainer

While we're on the topic of a 4.1 branch, I'd like to know if there's
any interest in supporting alternative backend datastores for Gnats.

I've been working on this for a couple of months now, and have made
some progress....the work has involved creating a datastore API
based on the current 'flat-file' code, moving the index into the
flat-file datastore and some configure related modifications to
support building Gnats against different datastore options. I've
also added an option to run Gnats in long-running-daemon mode,
to support things like database connection pools.

If there's interest, I'll submit the changes I have thus far for
review, and perhaps they can be rolled into the 4.1 development
effort. I've done a great deal of testing of the 'flat-file'
datastore implementation, based entirely on the existing Gnats code,
and it holds up well.

--
Mel Hatzis



_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

  reply	other threads:[~2003-02-03 21:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02 15:08 GNU GNATS 4.0 beta2 released Andrew J. Gray
2002-12-02 15:11 ` compiling gnats 4.0 beta 2 Steve Friedman
2002-12-04  2:36   ` Andrew J. Gray
2002-12-03 19:52 ` patch to display new PR number for new submissions Mel Hatzis
2002-12-04  3:02   ` Andrew J. Gray
2002-12-08  7:58   ` Andrew J. Gray
2002-12-08 12:27     ` Yngve Svendsen
2002-12-08 23:11       ` Patching the manual Lars Henriksen
2002-12-12  3:58         ` Yngve Svendsen
2002-12-12  6:29       ` patch to display new PR number for new submissions Andrew J. Gray
2002-12-08 23:11     ` Mel Hatzis
2003-02-02  9:32       ` Andrew J. Gray
2003-02-03 20:46         ` Mel Hatzis
2003-02-03 20:51           ` Yngve Svendsen
2003-02-03 21:17             ` Mel Hatzis [this message]
2003-02-03 22:10               ` Yngve Svendsen
2003-02-09  8:28               ` Andrew J. Gray
2003-02-09  7:48           ` Andrew J. Gray
2003-04-29 20:24             ` Yngve Svendsen
2002-12-09 10:54     ` dirk bergstrom
2002-12-14 14:26       ` Andrew J. Gray
2003-08-30 11:58   ` Andrew J. Gray

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=3E3EDBC2.3060905@juniper.net \
    --to=hatzis@juniper.net \
    --cc=help-gnats@gnu.org \
    --cc=yngve.svendsen@sun.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).