Initial patch |
patch
|
2011-02-27 08:59:58 UTC |
12.95 KB |
no flags
|
Details |
Second iteration of earlier patch |
patch
|
2011-02-27 15:52:01 UTC |
13.95 KB |
no flags
|
Details |
Third iteration of earlier patch |
patch
|
2011-02-28 06:20:23 UTC |
15.89 KB |
no flags
|
Details |
Fourth iteration of earlier patch |
patch
|
2011-03-02 17:04:55 UTC |
18.21 KB |
no flags
|
Details |
Fifth iteration of the earlier patch |
patch
|
2011-03-03 06:12:04 UTC |
18.34 KB |
no flags
|
Details |
Handle ERR_NOSUCHSERVER |
patch
|
2011-03-03 06:13:15 UTC |
4.45 KB |
no flags
|
Details |
Handle RPL_WHOISCHANNELS messages in response to RequestContactInfo |
patch
|
2011-03-17 19:14:42 UTC |
5.53 KB |
no flags
|
Details |
Handle RPL_WHOISLOGGEDIN messages in response to RequestContactInfo |
patch
|
2011-03-18 09:59:20 UTC |
3.61 KB |
no flags
|
Details |
Fix the RPL_WHOISCHANNELS patch |
patch
|
2011-03-18 17:58:43 UTC |
3.37 KB |
no flags
|
Details |
Implement ContactInfo |
patch
|
2011-03-21 15:37:59 UTC |
16.49 KB |
no flags
|
Details |
Handle ERR_NOSUCHSERVER |
patch
|
2011-03-21 15:48:10 UTC |
4.48 KB |
no flags
|
Details |
Implement ContactInfo |
patch
|
2011-03-29 14:12:59 UTC |
16.59 KB |
no flags
|
Details |
Handle RPL_WHOISSERVER messages in response to RequestContactInfo |
patch
|
2011-04-23 03:42:45 UTC |
3.52 KB |
no flags
|
Details |
Handle RPL_TRYAGAIN messages in response to RequestContactInfo |
patch
|
2011-04-25 13:21:15 UTC |
3.78 KB |
no flags
|
Details |
Handle WHOIS messages in our test IRC server |
patch
|
2011-04-25 13:21:49 UTC |
3.95 KB |
no flags
|
Details |
constants.py: add SERVICE_BUSY |
patch
|
2011-04-25 13:22:26 UTC |
856 bytes |
no flags
|
Details |
Test to cover RequestContactInfo |
patch
|
2011-04-25 13:23:19 UTC |
3.46 KB |
no flags
|
Details |
Handle RPL_WHOISSERVER messages in response to RequestContactInfo |
patch
|
2011-04-29 09:54:18 UTC |
3.44 KB |
no flags
|
Details |
Handle RPL_TRYAGAIN messages in response to RequestContactInfo |
patch
|
2011-04-29 09:55:48 UTC |
3.77 KB |
no flags
|
Details |
Test to cover RequestContactInfo |
patch
|
2011-04-29 09:58:39 UTC |
3.70 KB |
no flags
|
Details |
Handle WHOIS messages in our test IRC server |
patch
|
2011-05-02 04:47:23 UTC |
3.94 KB |
no flags
|
Details |
Handle RPL_WHOISHOST messages in response to RequestContactInfo |
patch
|
2011-05-05 16:11:44 UTC |
3.92 KB |
no flags
|
Details |
idletest: return an empty RPL_WHOISCHANNELS in response to WHOIS |
patch
|
2011-05-05 16:12:45 UTC |
1.54 KB |
no flags
|
Details |
Handle empty RPL_WHOISCHANNELS in response to RequestContactInfo |
patch
|
2011-05-05 16:13:21 UTC |
1.10 KB |
no flags
|
Details |
Handle RPL_WHOISHOST messages in response to RequestContactInfo |
patch
|
2011-05-06 11:31:20 UTC |
4.52 KB |
no flags
|
Details |
Try not to mistake RPL_WHOWAS_TIME as RPL_WHOISLOGGEDIN |
patch
|
2011-05-06 11:59:57 UTC |
1.53 KB |
no flags
|
Details |
Reduce boilerplate |
patch
|
2011-05-09 12:28:59 UTC |
9.67 KB |
no flags
|
Details |
Handle RPL_WHOISREGNICK messages in response to RequestContactInfo |
patch
|
2011-05-10 01:52:22 UTC |
4.49 KB |
no flags
|
Details |
Handle RPL_WHOISOPERATOR messages in response to RequestContactInfo |
patch
|
2011-05-10 01:52:54 UTC |
4.17 KB |
no flags
|
Details |
Handle RPL_WHOISSECURE messages in response to RequestContactInfo |
patch
|
2011-05-10 01:53:30 UTC |
4.41 KB |
no flags
|
Details |
Put the role played by the target nick in a channel as vCard parameter |
patch
|
2011-05-11 10:31:25 UTC |
1.92 KB |
no flags
|
Details |
contactinfo-request.py: check the x-irc-server and x-host fields |
patch
|
2011-05-11 11:09:37 UTC |
1.15 KB |
no flags
|
Details |
Add idle_muc_channel_is_typechar as per RFC 2811 |
patch
|
2011-05-11 11:10:15 UTC |
1.67 KB |
no flags
|
Details |
Use idle_muc_channel_is_typechar |
patch
|
2011-05-11 11:10:40 UTC |
1.12 KB |
no flags
|
Details |
Put the role played by the target nick in a channel as vCard parameter |
patch
|
2011-05-11 11:11:16 UTC |
1.50 KB |
no flags
|
Details |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.