public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Paul Traina <pst@juniper.net>
To: Bob Manson <bmanson@juniper.net>
Cc: Rick Macdonald <rickm@vsl.com>,
	gnats-devel@sourceware.cygnus.com, bug-gnats@gnu.org
Subject: Re: proclamation of intent
Date: Mon, 23 Aug 1999 10:48:00 -0000	[thread overview]
Message-ID: <19990823104833.A6147@red.juniper.net> (raw)
In-Reply-To: <199908231738.KAA09737@tristam.juniper.net>

How about if you drop a branch tag for gnats 3.x in now (in case folks want
to do later 3.x releases, and commit a snapshot into the head as 4.0-alpha).
This will give Rick and Ken a chance to change their front-ends to work with
4.0's commands, and we'll just screw the old network protocol.

On Mon, Aug 23, 1999 at 10:38:14AM -0700, Bob Manson wrote:
> In message < Pine.GSO.4.10.9908231115550.20253-100000@sys4 >, Rick Macdonald writ
> es:
> >On Wed, 18 Aug 1999, Bob Manson wrote:
> >
> >What does everybody think about numbering the next release 3.201, or
> >3.300 or 4.0?
> 
> I was shooting for 4.0 myself, since I think it's a big enough change
> to merit it.  Maybe "4.0-this-is-guaranteed-to-corrupt-your-PRMS-database"
> would be a better name ;-)
> 
> It's currently not network-protocol-backwards-compatible.  I've
> removed the myriad of "QXXX" commands and replaced them all with 
> "QUER queryformatname".  I could put back the old ones, I suppose. (On
> the other hand if I don't fix this, that means I can rip out all those
> screwy LXXX commands, the field designation commands, et al.)
> 
> In other news, I've implemented the configuration file, and the format
> looks almost exactly like what we came up with. Works too, tho I
> haven't removed the old field initialization stuff yet (it's in a new 
> source file scheduled for demolition).
> 
> Maybe I should work on getting a preliminary release out instead of
> finishing up what I originally started, namely the ability to add
> fields ;-) I have yet to add the network protocol for dumping out the
> field info (and the associated client options), there are still a fair
> number of places that know how many fields there are, and the mapping
> between internal field names and actual fields is not done (it still
> essentially derefs an array, bad juju).
> 
> If anyone really wants to play with this, I'll put it up.  Check it
> in? Something.  I say check it into CVS and let Patty sort it out.
> Other opinions?
> 
> >I wish I had a beer for every time I've answered mail from people trying
> >to build 3.2!
> 
> I wish I had a beer for every line of crap code I've deleted.  I'd be
> drunk for a couple of months, easy. ;-)
> 						Bob

  reply	other threads:[~1999-08-23 10:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-18 11:21 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 [this message]
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
     [not found] <Pine.LNX.4.04.9908241439580.17979-100000@intern.snow.nl>
1999-08-24  7:30 ` proclamation of intent Rick Macdonald

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=19990823104833.A6147@red.juniper.net \
    --to=pst@juniper.net \
    --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).