Barry Warsaw <barry at python.org> writes: > Jack turned over the release23-branch branch to me so I was able to > create the Python 2.3 maintenance branch. Here's what I did: > > - checked out release23-fork > - cvs tag -b release23-maint > - cvs up -rrelease23-maint > - cvs up -j release23-branch > - cvs commit > > IOW, I basically branched release23-maint off of the release23-fork tag > on the trunk, then I merged all the changes in the release23-branch to > the release23-maint. Here's a recipe I use for branches that others might find useful: $ cd ~/src/python/dist/ $ cvs co -d src-23x -r release23-maint python/dist/src (This creates -- eventually -- a src-23x directory alongside the src directory which contains the trunk) Then hack CVS/Entries to contain a line D/src-23x//// Now running cvs up in python/dist/ will update both the trunk and the release23-maint code (and in my case release22-maint, too). Cheers, mwh -- Just point your web browser at http://www.python.org/search/ and look for "program", "doesn't", "work", or "my". Whenever you find someone else whose program didn't work, don't do what they did. Repeat as needed. -- Tim Peters, on python-help, 16 Jun 1998
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