git branches reorganization

The work done by Jan and Daniele on async made completely obsolete my
tentative port of psycopg to python3. That is, the master branch is not
the real master anymore (to be sincere, it wasn't the real master even
before that..) But simply swapping python2 for master will confuse a lot
of people already tracking the repository, so here's my plan:

1) move master -> python3-historical
2) leave python2 as is

If me or someone else want to revive the python3 port we'll branch from
python2 into a new python3 branch (that's why the old port is named
python3-historical) and continue from there.

If, and only if, the codebase will be able to support python2 and
python3 at the same time we'll merge them in a single master branch in
the future.

Comments?

federico

-- 
Federico Di Gregorio                                       fog-NGVKUo/i/[email protected]
 I did appreciate the irony that I was whining about encoding issues on
  a mailing list that was unable to show those chars, too.
                                 -- Antti S. Lankila to mono-devel-list@

_______________________________________________
Psycopg mailing list
Psycopg-IAPFreCvJWPBWskQ1e/[email protected]
http://lists.initd.org/mailman/listinfo/psycopg

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvuYeAACgkQvcCgrgZGjetN0ACfbhAtEbJTa4ki2+zoJ2dy2oGW
cY0AoIuKzBikLPW/nRr0eqKUKMj1P7ia
=U6M7
-----END PGP SIGNATURE-----