From: Roland Winkler <winkler@gnu.org>
To: Sergio Durigan Junior <sergiodj@riseup.net>
Cc: 11580@debbugs.gnu.org, emacs-devel@gnu.org
Subject: bug#11580: [PATCH] Fix bug #11580
Date: Sat, 29 Sep 2012 07:04:46 -0500 [thread overview]
Message-ID: <87d3152fxd.fsf__29903.4264208332$1348920363$gmane$org@gnu.org> (raw)
In-Reply-To: <87mx0c655g.fsf__10545.1882271611$1348682125$gmane$org@thinkpad.tsdh.de> (Tassilo Horn's message of "Wed, 26 Sep 2012 19:54:51 +0200")
On Wed, Sep 26 2012, Tassilo Horn wrote:
>> The attached patch fixes the bug listed on $SUBJECT. Maybe there are
>> better ways to fix it, but a quick hack did the trick so I am sending
>> it for review.
>
> I don't use bbdb, so I've Cc-ed Roland who is the current bbdb
> maintainer. Roland, the complete bug thread is here:
It seems this is all about BBDB v2. Unfortunately, the BBDB v3 that I
have been working on for a little while has not yet been released
BBDB is available at
http://savannah.nongnu.org/projects/bbdb/
To check it out, use
git clone git://git.savannah.nongnu.org/bbdb.git
Nobody on the BBDB mailing list has ever mentioned EUDC. So I never
thought about this till I saw this bug report.
I've tried to clean up the code of BBDB and make it more robust. Lots of
things have changed along this way. It seems to me that eudc-bbdb.el
would likewise benefit from that. However, the current version of
eudc-bbdb.el will not work with BBDB v3.
There are a few things left I'd like to do before making the first
proper release of BBDB v3. It appears to me that then it would make more
sense to look into adapting eudc-bbdb.el to BBDB v3.
If in the meanwhile you have a patch that fixes the bug for you, can you
continue with it till then?
Thanks,
Roland
next prev parent reply other threads:[~2012-09-29 12:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ipb64w5x.fsf@riseup.net>
2012-09-26 17:54 ` bug#11580: [PATCH] Fix bug #11580 Tassilo Horn
2012-09-29 12:04 ` Roland Winkler [this message]
[not found] ` <87d3152fxd.fsf@gnu.org>
2012-09-29 19:30 ` Sergio Durigan Junior
[not found] ` <m3pq54hbj1.fsf@riseup.net>
[not found] ` <20584.24939.541992.925590@gargle.gargle.HOWL>
2012-05-29 5:14 ` bug#11580: 23.3; EUDC can't handle empty last names in BBDB Sergio Durigan Junior
[not found] ` <handler.11580.B.133834110724596.ack@debbugs.gnu.org>
2012-07-12 2:00 ` bug#11580: Acknowledgement (23.3; EUDC can't handle empty last names in BBDB) Sergio Durigan Junior
2012-07-12 14:37 ` Stefan Monnier
2012-10-02 1:46 ` bug#11580: [PATCH] Fix bug #11580 Sergio Durigan Junior
[not found] ` <87d3113ass.fsf@riseup.net>
2012-10-02 1:58 ` Roland Winkler
2012-10-02 2:50 ` Sergio Durigan Junior
2012-10-02 3:59 ` Stefan Monnier
2012-10-02 5:10 ` Chong Yidong
2012-09-30 15:12 ` Roland Winkler
[not found] ` <87mx0c655g.fsf@thinkpad.tsdh.de>
2012-09-26 18:18 ` Sergio Durigan Junior
[not found] ` <m3ipb0r6kf.fsf@riseup.net>
2012-09-26 18:56 ` Tassilo Horn
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='87d3152fxd.fsf__29903.4264208332$1348920363$gmane$org@gnu.org' \
--to=winkler@gnu.org \
--cc=11580@debbugs.gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sergiodj@riseup.net \
/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).