cvs log for libpq-int.h ...

Started by The Hermit Hackerover 26 years ago3 messages
#1The Hermit Hacker
scrappy@hub.org

Just curious, but why...?

revision 1.10
date: 1999/07/13 20:00:37; author: momjian; state: Exp; lines: +2 -2
Redefine cpu's as __cpu__. Only for 6.6 branch.

Why 'Only for 6.6...'?

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

#2Bruce Momjian
maillist@candle.pha.pa.us
In reply to: The Hermit Hacker (#1)
Re: [HACKERS] cvs log for libpq-int.h ...

Just curious, but why...?

revision 1.10
date: 1999/07/13 20:00:37; author: momjian; state: Exp; lines: +2 -2
Redefine cpu's as __cpu__. Only for 6.6 branch.

Why 'Only for 6.6...'?

6.5.* is a dead branch.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
#3The Hermit Hacker
scrappy@hub.org
In reply to: Bruce Momjian (#2)
Re: [HACKERS] cvs log for libpq-int.h ...

On Fri, 30 Jul 1999, Bruce Momjian wrote:

Just curious, but why...?

revision 1.10
date: 1999/07/13 20:00:37; author: momjian; state: Exp; lines: +2 -2
Redefine cpu's as __cpu__. Only for 6.6 branch.

Why 'Only for 6.6...'?

6.5.* is a dead branch.

From a development standpoint, yes...from a commercial standpoint,

no...6.5.x represents our only stable branch until v6.6 takes over its
place...

I'm planning on maintaining it such that if a client calls up, running
v6.5.x and saying there is a bug, we can easily supply a patch to him to
fix it...telling a commercial/production site that "its fixed in v6.6,
which will be out in 4 months", IMHO, is no longer acceptable...

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org