[sanko/net-bittorrent] 56a7b7: Move into github and code clean up

4 views
Skip to first unread message

nor...@github.com

unread,
Jan 26, 2009, 9:15:12 PM1/26/09
to net-bit...@googlegroups.com
Branch: refs/heads/master
Home: http://github.com/sanko/net-bittorrent

Commit: 56a7b7cf26a0abfcb71202e2eea9c006aa8b8426
http://github.com/sanko/net-bittorrent/commit/56a7b7cf26a0abfcb71202e2eea9c006aa8b8426
Author: Sanko Robinson <sa...@cpan.org>
Date: 2009-01-26 (Mon, 26 Jan 2009)

Changed paths:
M Build.PL
M Changes
M MANIFEST.SKIP
M Makefile.PL
M Notes.pod
M README
M TODO.pod
M lib/Net/BitTorrent.pm
M lib/Net/BitTorrent/DHT.pm
M lib/Net/BitTorrent/Peer.pm
M lib/Net/BitTorrent/Protocol.pm
M lib/Net/BitTorrent/Torrent.pm
M lib/Net/BitTorrent/Torrent/File.pm
M lib/Net/BitTorrent/Torrent/Tracker.pm
M lib/Net/BitTorrent/Torrent/Tracker/HTTP.pm
M lib/Net/BitTorrent/Torrent/Tracker/UDP.pm
M lib/Net/BitTorrent/Util.pm
M lib/Net/BitTorrent/Version.pm
M scripts/bittorrent.pl
M t/000_miniswarm/007_miniswarm_http.t
M t/000_miniswarm/008_miniswarm_dht.t
M t/000_miniswarm/009_miniswarm_udp.t
M t/700_classes/Net/BitTorrent.t
M t/700_classes/Net/BitTorrent/DHT.t
M t/700_classes/Net/BitTorrent/Peer.t
M t/700_classes/Net/BitTorrent/Protocol.t
M t/700_classes/Net/BitTorrent/Torrent.t
M t/700_classes/Net/BitTorrent/Torrent/File.t
M t/700_classes/Net/BitTorrent/Torrent/Tracker.t
M t/700_classes/Net/BitTorrent/Torrent/Tracker/HTTP.t
M t/700_classes/Net/BitTorrent/Torrent/Tracker/UDP.t
M t/700_classes/Net/BitTorrent/Util.t
M t/700_classes/Net/BitTorrent/Version.t
M t/900_data/910_scripts/TCP-talk-to-ourself.pl
M t/900_data/910_scripts/UDP-talk-to-ourself.pl
M tatoeba/000-basic.pl
M tatoeba/001-torrent-info.pl
M tatoeba/002-debug.pl
M tatoeba/003-threads.pl
M tatoeba/004-resume.pl

Log Message:
-----------
Move into github and code clean up

* Several updates in the language used in N::B::Version's pod
* N::B::Notes has been trimmed down a bit
* N::B's pod has been trimmed
* ALL tests are run even on non-dev systems
- I'm doing this to shake out the last few (I hope) crash/protocol bugs
before really putting effort into more advanced stuff


Reply all
Reply to author
Forward
0 new messages