bitlbee - personal fork of github.com/bitlbee/bitlbee

	Commit message (Collapse)	Author	Age	Lines
*	purple: document original names of uiops next to them	dequis	2015-12-26	-9/+9
\|
*	purple/ft: remove prplcb_xfer_dbg entries with mismatching signatures	dequis	2015-12-01	-7/+2
\| \| \| \|	More fixing warnings.
*	purple: move PurpleAccount from proto_data in a struct purple_data	Antoine Pietri	2015-03-02	-2/+4
\|
*	Reindent everything to K&R style with tabs	Indent	2015-02-20	-158/+149
\| \| \| \| \| \| \|	Used uncrustify, with the configuration file in ./doc/uncrustify.cfg Commit author set to "Indent <please@skip.me>" so that it's easier to skip while doing git blame.
*	Merging killerbee stuff, bringing all the bleeding-edge stuff together.	Wilmer van der Gaast	2010-06-07	-6/+8
\|
*	Fixed sending with proper filenames by creating a temporary directory with	Wilmer van der Gaast	2010-05-21	-22/+42
\| \| \| \| \| \| \| \|	the file in it; protocol modules are mostly hardcoded to use the filename from the filesystem with no way to override this. Also improved robustness a little bit.
*	Similar hacky code to send files. This indirect sending stuff sucks badly	Wilmer van der Gaast	2010-05-19	-20/+93
\| \| \| \| \| \| \| \|	for numerous reasons. Maybe libpurple 2.7.0 is less crappy and will eventually allow (working) direct ft's again. This somewhat works, but filename info is lost with some protocols.
*	Little cleanup. Less compiler warnings, and removing tempfile at the	Wilmer van der Gaast	2010-05-18	-77/+81
\| \| \| \| \|	beginning of the download already to make sure it doesn't stick around.
*	This receives files but is very fragile if anything unusual happens (like a	Wilmer van der Gaast	2010-05-18	-15/+102
\| \| \| \| \|	cancellation/timeout/etc).
*	Move direct ft stuff to an unused file: This gets too hairy and too fragile.	Wilmer van der Gaast	2010-05-17	-101/+36
\| \| \| \| \| \| \|	I don't have time to work out all the details, I doubt if this is supposed to work reliably yet at all. Let's go for the simple via-disk approach for now.
*	Split off the file transfer stuff into a separate file. What a mess.	Wilmer van der Gaast	2010-05-17	-0/+234