summaryrefslogtreecommitdiffstats
path: root/Include/patchlevel.h
Commit message (Collapse)AuthorAgeFilesLines
* r88840: Prepare for 2.5.6.v2.5.6Martin v. Löwis2011-05-281-3/+3
|
* r88824: Prepare for 2.5.6c1.v2.5.6c1Martin v. Löwis2011-05-281-3/+3
|
* Post 2.5.5.Martin v. Löwis2010-01-311-3/+3
|
* Prepare for 2.5.5.v2.5.5Martin v. Löwis2010-01-311-3/+3
|
* Prepare for 2.5.5c2.v2.5.5c2Martin v. Löwis2010-01-241-2/+2
|
* Prepare for 2.5.5c1.v2.5.5c1Martin v. Löwis2010-01-141-4/+4
|
* Prepare for 2.5.4.v2.5.4Martin v. Löwis2008-12-231-2/+2
|
* Post 2.5.3.Martin v. Löwis2008-12-201-3/+3
|
* Prepare for 2.5.3.v2.5.3Martin v. Löwis2008-12-191-3/+3
|
* Prepare for 2.5.3c1.v2.5.3c1Martin v. Löwis2008-12-131-3/+3
|
* Bump version for 2.5.3a0.Martin v. Löwis2008-02-231-3/+3
|
* Prepare for 2.5.2.Martin v. Löwis2008-02-211-3/+3
|
* Preparing for 2.5.2c1.Martin v. Löwis2008-02-141-3/+3
|
* when talking about an imminent 2.5.2c1, the build should identify itselfFred Drake2007-11-091-3/+3
| | | | | as being some form of 2.5.2 (this is admittedly a bit conservative); we can make this 2.5.2c1 when making the release
* 2.5.1 finalv2.5.1Anthony Baxter2007-04-181-3/+3
|
* preparing for 2.5.1c1Anthony Baxter2007-04-051-4/+4
|
* Preparing for 2.5 final.v2.5Anthony Baxter2006-09-181-3/+3
| | | | | | (damn, it's nice to see the line #define PY_VERSION "2.5" in patchlevel.h)
* preparing for 2.5c2Anthony Baxter2006-09-111-2/+2
|
* preparing for 2.5c1 - no, really this timeAnthony Baxter2006-08-161-1/+1
|
* preparing for 2.5c1Anthony Baxter2006-08-161-2/+2
|
* pre-release machinationsAnthony Baxter2006-08-021-2/+2
|
* preparing for 2.5b2Anthony Baxter2006-07-101-2/+2
|
* Preparing for 2.5b1.Anthony Baxter2006-06-191-3/+3
|
* 2.5a2Anthony Baxter2006-04-271-2/+2
|
* preparation for 2.5a1Anthony Baxter2006-04-031-2/+2
|
* Drop sys.build_number. Add sys.subversion.Martin v. Löwis2006-01-051-0/+3
|
* post 2.4 release machinationsAnthony Baxter2004-11-301-3/+3
|
* preparing for 2.4 final (wooooooo!)Anthony Baxter2004-11-291-3/+3
|
* preparing for rc1Anthony Baxter2004-11-151-4/+4
|
* release bitAnthony Baxter2004-11-021-2/+2
|
* bump the version number prior to releaseFred Drake2004-10-141-3/+3
|
* onward and upwardAnthony Baxter2004-08-311-2/+2
|
* on to a2!Anthony Baxter2004-08-031-2/+2
|
* post-release funAnthony Baxter2004-07-091-1/+1
|
* bump the version number for 2.4a1Fred Drake2004-07-081-2/+2
|
* Bump the trunk to 2.4a0Barry Warsaw2003-07-301-3/+3
|
* Repair botched release serial number.Tim Peters2003-07-291-1/+1
|
* Bump release level to 2.3 (we won't have time for this tomorrow).Tim Peters2003-07-291-2/+2
|
* Bump the version numberBarry Warsaw2003-07-251-1/+1
|
* Update version numbers and dates for 2.3c2 -- we won't be able to do thisTim Peters2003-07-241-2/+2
| | | | during the day tomorrow, so doing it earlier than I'd like.
* Bump the release number to 2.3c1.Tim Peters2003-07-171-3/+3
|
* Bump version string to "2.3b2+".Tim Peters2003-06-301-1/+1
|
* Bump release level to 2.3b2.Tim Peters2003-06-291-2/+2
|
* Mark CVS as 2.3b1+.Guido van Rossum2003-04-301-1/+1
|
* Bump version number to 2.3b1.Tim Peters2003-04-241-3/+3
|
* Update PY_VERSION to indicate that we're beyond 2.3a2 now.Guido van Rossum2003-02-201-1/+1
|
* Bump version # to 2.3a2.Tim Peters2003-02-181-2/+2
|
* Various updates to the version number, on the eve of the 2.3a1 release.Guido van Rossum2002-12-311-1/+1
|
* Change the version string from "2.2+" to "2.3a0". disutils peels offTim Peters2002-02-021-1/+1
| | | | | | the first 3 characters of this string in several places, so for as long as they remain "2.2" it confuses the heck out of attempts to build 2.3 stuff using distutils.
* And we start all over again!Barry Warsaw2001-12-211-3/+3
|
generated by cgit v0.12 at 2025-12-26 16:19:20 (GMT)