A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-January/059457.html below:

[Python-checkins] commit of r41907- python/trunk/Makefile.pre.in)

[Python-Dev] buildno (Was: [Python-checkins] commit of r41907- python/trunk/Makefile.pre.in) [Python-Dev] buildno (Was: [Python-checkins] commit of r41907- python/trunk/Makefile.pre.in)"Martin v. Löwis" martin at v.loewis.de
Fri Jan 6 08:27:52 CET 2006
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
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4