In message <[EMAIL PROTECTED]> Ronan Waide writes:
: > ;;; file-version: 3
: Shouldn't be a problem. I checked this before releasing.
OK. I'll give it a try and let you know. Now, where did I put my
source forge...
Warner
___
bbdb-info mailing list
On January 26, [EMAIL PROTECTED] said:
> Yes. I seem to recall there was some problem making the automatic
> conversion from
>
> ;;; file-version: 3
>
> that I have. Has that been fixed?
>
> Warner
Shouldn't be a problem. I checked this before releasing.
Waider.
--
[EMAIL PROTECTED] / Yes,
In message <[EMAIL PROTECTED]> Ronan Waide writes:
: It should automatically convert the file for you. Just to be on the
: safe side, MAKE A BACKUP FIRST.
I keep my .bbdb file in CVS :-) I'll do a cvs commit before I try the
conversion. Actually, I'll try the conversion on a different machine
On January 26, [EMAIL PROTECTED] said:
>
> Way cool! I'll have to give it a spin.
>
> I do have one question, however. I'm running
>
> BBDB version 2.00.01 ($Date: 1998/04/11 07:26:05 $)
>
> What kind of pain am I setting myself up for by upgrading to 2.2 :-)
> I have 17k lines in my .bbdb
In message <[EMAIL PROTECTED]> Ronan Waide writes:
: I've offically nailed BBDB-2.2 in CVS. Release notes, freshmeat
: uploads, website changes, etc. are still in progress, but...
Way cool! I'll have to give it a spin.
I do have one question, however. I'm running
BBDB version 2.00.01 ($Date:
Okay,
I've offically nailed BBDB-2.2 in CVS. Release notes, freshmeat
uploads, website changes, etc. are still in progress, but...
since I tagged it just before midnight, it's exactly two years after
the last BBDB release, which is the deadline I've been unofficially
trying to hit.
Release note
