public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Milan Zamazal <pdm@zamazal.org>
Cc: <gnats-devel@sources.redhat.com>
Subject: Re: Compatibility between GNATS 3.x and 4.x? gnatsweb?
Date: Sun, 11 Feb 2001 17:30:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.33.0102120224340.83060-100000@deneb.dbai.tuwien.ac.at> (raw)
In-Reply-To: <87itmhnfub.fsf@zamazal.org>

On 11 Feb 2001, Milan Zamazal wrote:
>> Are GNATS 3.x and 4.0 supposed to be incompatible? [...]
>> Or should it be possible to update the GNATS server and keep existing
>> clients?
> - Though it might be technically possible to retain most of the gnatsd 3
>   commands (I didn't check carefully), it would leave a lot of garbage
>   in the gnatsd command set instead of really simplifying it.

Well, this is a good point.

> - I don't consider a backward compatibility being a serious issue here,
>   because I suppose most installed interfaces are tight to their server
>   and are supposed to be upgraded together with the server.

Hmm, not necessarily. For example, I would have liked to use the current
CVS version of gnatsweb on gcc.gnu.org, first to do some testing by
myself, and then also in production use. This I could do easily, but
having the entire GNATS installation updated, would be quite more
involved.

(I hope the upgrade path from GNAT 3.x to 4.x will be simple and well
documented, so that one can easily migrated his databases? Then it'll
be less of a problem for most regular sites.)

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

  reply	other threads:[~2001-02-11 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08  3:44 Gerald Pfeifer
2001-02-12 13:22 ` Milan Zamazal
2001-02-11 17:30   ` Gerald Pfeifer [this message]
2001-02-12 13:23     ` Milan Zamazal

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.33.0102120224340.83060-100000@deneb.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=gnats-devel@sources.redhat.com \
    --cc=pdm@zamazal.org \
    /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).