Skip to Content.
Sympa Menu

freetds - RE: Corrupt file 0.60rc1

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: Corrupt file 0.60rc1
  • Date: Tue, 10 Sep 2002 17:10:46 -0400


> From: Brian Bruns [mailto:camber AT ais.org]
> Sent: September 10, 2002 4:40 PM

> > odbc. What does the overnight snapshot do that "make dist"
> doesn't? Is
> > there a good reason for it? I guess it's time I understood
> this better, being Chief Release Engineer and all.
>
> Hmmm....you've got the script.

Yeah, but I left it at home. And my dog ate it. No, I made that up, about
the dog.

> Something about my box that always
> generates with the odbc stuff? Make sense that odbc would
> always 'dist'
> but not 'install' unless the configure flag was set. BTW,
> I'm cooking
> up a patch to detect iODBC/unixODBC instead of having to
> specify it

OK, tomorrow morning I'm going to be Mr. Configur until "make dist" makes
dists. I've already got some retagging to do, and now that I understand (so
I say) the liabilities, I think I can get the real final dist ready.

If you and Frediano will be available (IRC?) to double check me between 9:00
and 12:00 EST tomorrow morning, I think we can make the final cut then. If
later we find another tool-related problem, we can retag and offer 0.60.1 at
a discount.

--jkl



The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.






Archive powered by MHonArc 2.6.24.

Top of Page