[Python-Dev] buildno (Was: [Python-checkins] commit of r41907- python/trunk/Makefile.pre.in) (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Fri Jan 6 08:27:52 CET 2006
- Previous message: [Python-Dev] buildno (Was: [Python-checkins] commit of r41907- python/trunk/Makefile.pre.in)
- Next message: [Python-Dev] buildno (Was: [Python-checkins] commit of r41907- python/trunk/Makefile.pre.in)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Barry Warsaw wrote:
It would still be one level behind: patchlevel.h gets N, then 'svn cp' creates the tag, producing N+1. OTOH, for a tag, the revision number is nearly irrelevant.
Unless we tagged and then modified the file in that tag as the very last thing we do before we create the tarball. Or is that too evil?
That would work, and I wouldn't see anything wrong with it. I believe it would also work to modify the working copy, and then svn cp it (instead of svn committing it) - atleast the svn docs suggest that you can copy a working copy into a repo URL.
Regards, Martin
- Previous message: [Python-Dev] buildno (Was: [Python-checkins] commit of r41907- python/trunk/Makefile.pre.in)
- Next message: [Python-Dev] buildno (Was: [Python-checkins] commit of r41907- python/trunk/Makefile.pre.in)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]