public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Milan Zamazal <pdm@zamazal.org>
To: Peter Novodvorsky <nidd@altlinux.ru>
Cc: gnats-devel@sources.redhat.com
Subject: Re: modular database backends
Date: Mon, 11 Jun 2001 11:53:00 -0000	[thread overview]
Message-ID: <87pucbyt1r.fsf@blackbird.zamazal.org> (raw)
In-Reply-To: <7x4ru4kl9y.fsf@lambda.novdv.ru>

>>>>> "PN" == Peter Novodvorsky <nidd@altlinux.ru> writes:

    PN> May be you could make a CVS branch for 4.99?

Not yet.  That would require a lot of duplicate commits in the bug
fixing and cleanup phase.

    PN> Heh, that's bad because I wanted to begin making implementation
    PN> very actively. Do you have thoughts on the subject?  I'm writing
    PN> ``specification'' of some kind. Maybe it will give the subject
    PN> for discussion.

Well, the first ideas are:

- A function for deleting a PR should be added.  This is only seldom
  used, but it's sometimes useful and can also be used e.g. by
  maintenance tools.

- Maybe it's not *necessary* to force backends to implement full query
  handling.  We probably can agree on that writing new backends should
  be as simple as possible.  I can imagine that your `query_pr' function
  could be only optional and there could be available simpler versions
  of query functions that can get a list of all problem IDs, a
  particular PR and maybe also optionally some index (similar to the
  current one).

Regards,

Milan Zamazal

-- 
  _/_\_/_  o     _\_/_\_  o     _/_\_/_  o     _\_/_\_  o    BEWARE!
-<_|_|_|_><--  -<_|_|_|_><--  -<_|_|_|_><--  -<_|_|_|_><--   *Bugs* are
   / \ /   o      \ / \   o      / \ /   o      \ / \   o     approaching!

  reply	other threads:[~2001-06-11 11:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-27 11:32 Peter Novodvorsky
2001-05-28  2:43 ` Yngve Svendsen
2001-05-28  4:34   ` Peter Novodvorsky
2001-06-04 21:53   ` Margaret BRIERTON
2001-06-05  1:35     ` GNATS discussion group Yngve Svendsen
2001-06-05 19:56       ` Margaret BRIERTON
2001-06-06  4:54         ` Yngve Svendsen
2001-06-07 17:04           ` Margaret BRIERTON
2001-06-07 18:15             ` Database Margaret BRIERTON
2001-05-28 14:37 ` modular database backends Milan Zamazal
2001-05-29 12:43   ` Peter Novodvorsky
2001-06-11 11:53     ` Milan Zamazal [this message]
2001-06-13 10:31       ` Peter Novodvorsky
2001-06-17 12:26         ` Milan Zamazal
2001-06-11 11:53 ` access control (was Re: modular database backends) Milan Zamazal
2001-06-13  5:20   ` access control Hans-Albert Schneider
2001-06-17 12:26     ` Milan Zamazal
2001-06-13 10:44   ` access control (was Re: modular database backends) Peter Novodvorsky
2001-05-27 11:35 modular database backends Peter Novodvorsky
2001-05-29  0:11 Dirk Bergstrom
2001-05-29  0:22 ` Bob Kaehms
2001-05-29  1:16   ` Peter Novodvorsky

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=87pucbyt1r.fsf@blackbird.zamazal.org \
    --to=pdm@zamazal.org \
    --cc=gnats-devel@sources.redhat.com \
    --cc=nidd@altlinux.ru \
    /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).