head	1.2;
access;
symbols
	v1_5_0:1.1
	v1_4_0:1.1
	gaim-doodle:1.1.0.6
	v1_3_1:1.1
	v1_3_0:1.1
	v1_2_1:1.1
	v1_2_0:1.1
	v1_1_4:1.1
	v1_1_3:1.1
	v1_1_2:1.1
	v1_1_1:1.1
	v1_1_0:1.1
	v1_0_3:1.1
	v1_0_2:1.1
	v1_0_1:1.1
	v1_0_0:1.1
	oldstatus:1.1.0.4
	v0_82:1.1
	v0_81:1.1
	v0_80:1.1
	v0_79:1.1
	v0_78:1.1
	v0_77:1.1
	v0_76:1.1
	v0_75:1.1
	v0_74:1.1
	v0_74-branch:1.1.0.2
	v0_73:1.1
	v0_72:1.1
	v0_62:1.1
	v0_71:1.1
	v0_70:1.1
	v0_69:1.1
	v0_68:1.1
	v0_67:1.1
	v0_65:1.1;
locks; strict;
comment	@# @;


1.2
date	2005.09.01.03.32.52;	author thekingant;	state dead;
branches;
next	1.1;

1.1
date	2003.06.14.06.06.40;	author chipx86;	state Exp;
branches;
next	;


desc
@@


1.2
log
@Get rid of the old gaim-remote.  Someone will need to make sure the
new D-BUS stuff is distributed in the tarballs and rpms appropriately.

Did I miss any pieces?
@
text
@Makefile
Makefile.in
.deps
.libs
*.dll
*.la
*.lo
@


1.1
log
@CUI is gone, long live gaim-remote! The old CUI functionality, which was
for remote-controlling gaim, is now a Core Plugin, so any future UI
(including the current, normal gaim gtk UI) can be remote-controlled.
Applications will soon be able to link against the library and header files
and provide their own remote-control of gaim, but why bother? :) If you
use gaim-remote, make sure to load the new plugin. It won't auto-load.
@
text
@@

