From: "Roland Winkler" <winkler@gnu.org>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: George McNinch <gmcninch@gmail.com>,
bbdb-info@lists.sourceforge.net, emacs-devel@gnu.org
Subject: Re: eudc conversion to bbdb (in bbdb3.1.2?)
Date: Fri, 20 Nov 2015 23:03:10 -0600 [thread overview]
Message-ID: <64270.20127.528598.22095@gargle.gargle.HOWL> (raw)
In-Reply-To: <m3610z6prl.fsf@fitzsim.org>
On Wed Nov 18 2015 Thomas Fitzsimmons wrote:
> The version of EUDC in question should be able to read bbdb 2.x or
> bbdb 3.x formatted databases transparently. But I haven't done
> much testing with eudc-query and writing BBDB entries from there.
Ah, thanks, that's good to know. Lately I did not look at Emacs git.
> I guess now is a good time to revisit: is there any chance of BBDB
> ever getting assignment paperwork from its existing contributors?
> As I understand it, though BBDB 3 is largely a rewrite it still
> uses code patterns from prior contributors that may not be clear
> from a copyright standpoint?
I believe it is fair to say that the core of BBDB has been rewritten
completely (the three files bbdb.el, bbdb-com.el and bbdb-mua.el), also
some add-ons are "clean" (bbdb-anniv.el, bbdb-ispell.el,
bbdb-snarf.el, bbdb-pgp.el)
Loose ends include the add-ons bbdb-sc.el, bbdb-print.el and
mua-specific pieces of code in bbdb-gnus.el and bbdb-vm.el.
One option could be to incorporate the core of BBDB into GNU Emacs
and keep the loose ends in savannah.nongnu.org. BBDB has a long
history of having a core plus many add-ons.
Roland
next prev parent reply other threads:[~2015-11-21 5:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <82mvuffcyc.fsf@jobim-via-gmail.com>
2015-11-18 17:18 ` eudc conversion to bbdb (in bbdb3.1.2?) Roland Winkler
2015-11-18 20:01 ` Thomas Fitzsimmons
2015-11-21 5:03 ` Roland Winkler [this message]
2015-11-21 10:29 ` Adding BBDB 3 core to Emacs (was: eudc conversion to bbdb (in bbdb3.1.2?)) Thomas Fitzsimmons
2015-11-21 16:56 ` Adding BBDB 3 core to Emacs John Wiegley
2015-11-21 17:11 ` Eli Zaretskii
2015-11-21 19:59 ` Thomas Fitzsimmons
2015-11-23 2:03 ` Richard Stallman
2015-11-21 20:02 ` Roland Winkler
2015-11-22 7:02 ` Stephen J. Turnbull
2015-11-22 15:33 ` Roland Winkler
2015-11-22 16:14 ` Stephen J. Turnbull
2015-11-22 21:42 ` Roland Winkler
2015-11-23 1:47 ` Stephen J. Turnbull
2015-11-23 9:04 ` David Kastrup
2015-11-23 2:05 ` Richard Stallman
2015-11-23 3:57 ` Roland Winkler
2015-11-23 16:10 ` Richard Stallman
2015-11-23 18:03 ` Roland Winkler
2015-11-24 2:37 ` Richard Stallman
2015-11-21 19:37 ` Thomas Fitzsimmons
2015-11-21 23:00 ` raman
2015-11-22 5:16 ` John Wiegley
2015-11-21 22:22 ` Roland Winkler
2015-11-18 20:40 ` eudc conversion to bbdb (in bbdb3.1.2?) Barak A. Pearlmutter
2015-11-21 5:04 ` Roland Winkler
2015-11-21 10:39 ` Barak A. Pearlmutter
2015-11-21 22:55 ` Roland Winkler
2015-11-22 10:14 ` Barak A. Pearlmutter
2015-11-22 21:50 ` Roland Winkler
2015-11-21 13:17 ` Eric Abrahamsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=64270.20127.528598.22095@gargle.gargle.HOWL \
--to=winkler@gnu.org \
--cc=bbdb-info@lists.sourceforge.net \
--cc=emacs-devel@gnu.org \
--cc=fitzsim@fitzsim.org \
--cc=gmcninch@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).