Mercurial > pidgin.yaz
view doc/Makefile.am @ 29246:1428d59119cd
*** Plucked rev aada73f0d8a35997280d570f47caf30907fe68df (bcc0147bab874ca52c55ad4900545e17528bf8fd):
Make sure that libpurple core knows that a buddy is on the allow list just
after accepting their add request. Previously, this was not a problem, and
would go away at next login, but now that the core does its own client-side
blocking, it appears as if newly added buddies can't talk to you.
Fixes #10898.
author | Daniel Atallah <daniel.atallah@gmail.com> |
---|---|
date | Thu, 07 Jan 2010 23:44:38 +0000 |
parents | 76a689608a83 |
children |
line wrap: on
line source
man_MANS = if ENABLE_GTK man_MANS += pidgin.1 endif if ENABLE_GNT man_MANS += finch.1 endif EXTRA_DIST = \ C-HOWTO.dox \ PERL-HOWTO.dox \ SIGNAL-HOWTO.dox \ TCL-HOWTO.dox \ TracFooter.html \ TracHeader.html \ account-signals.dox \ blist-signals.dox \ certificate-signals.dox \ cipher-signals.dox \ connection-signals.dox \ conversation-signals.dox \ core-signals.dox \ dbus-server-signals.dox \ funniest_home_convos.txt \ finch.1.in \ gtkaccount-signals.dox \ gtkblist-signals.dox \ gtkconv-signals.dox \ gtklog-signals.dox \ gtkimhtml-signals.dox \ gtkrc-2.0 \ imgstore-signals.dox \ jabber-signals.dox \ log-signals.dox \ notify-signals.dox \ pidgin.1.in \ plugin-i18n.dox \ plugin-ids.dox \ plugin-signals.dox \ savedstatus-signals.dox \ sound-signals.dox \ the_penguin.txt \ xfer-signals.dox