- Timestamp:
- 07/05/05 01:37:09 (8 years ago)
- Hash name:
- 20050704233709-97f81-5389b8a7444d1f9ac89c6c2084d2f1f0940e1959
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
README
r381 r399 55 55 ============ 56 56 57 tailor .pyis written in Python, and thus Python must be installed on57 tailor is written in Python, and thus Python must be installed on 58 58 your system to use it. It has been successfully used with Python 2.3 59 59 and 2.4. … … 63 63 those you will actually use. 64 64 65 Make tailor .pyexecutable::66 67 $ chmod +x tailor .py68 69 You can either run tailor .pywhere it is currently located, or move it65 Make tailor executable:: 66 67 $ chmod +x tailor 68 69 You can either run tailor where it is currently located, or move it 70 70 along with the vcpx directory to a location in your PATH. 71 71 … … 79 79 1. Bootstrap a new tailored project, starting at upstream revision 10:: 80 80 81 $ tailor .py-b -s svn -R http://svn.server/path/to/svnrepo \81 $ tailor -b -s svn -R http://svn.server/path/to/svnrepo \ 82 82 --module /Product/trunk -r 10 --subdir Product ~/darcs/MyProduct 83 83 … … 86 86 already under SVN:: 87 87 88 $ tailor .py--source-kind cvs --target-kind svn --bootstrap \88 $ tailor --source-kind cvs --target-kind svn --bootstrap \ 89 89 --repository :pserver:cvs.zope.org:/cvs-repository \ 90 90 --module CMF/CMFCore ~/svnwc/cmfcore … … 95 95 name):: 96 96 97 $ tailor .py-D -b -R :pserver:anonymous@cvs.zope.org:/cvs-repository/ \97 $ tailor -D -b -R :pserver:anonymous@cvs.zope.org:/cvs-repository/ \ 98 98 -m CMF/CMFTopic ~/darcs/cmftopic 99 99 100 100 4. Merge upstream changes since last update/bootstrap:: 101 101 102 $ tailor .py~/svnwc/MyProduct102 $ tailor ~/svnwc/MyProduct 103 103 104 104 5. Migrate a whole SVN repository, starting from the beginning:: 105 105 106 $ tailor .py-b -s svn -R svn+ssh://caia/tmp/svn/repo --module / \106 $ tailor -b -s svn -R svn+ssh://caia/tmp/svn/repo --module / \ 107 107 --subdir testsvn --revision 1 testdir 108 108 … … 113 113 6. Bootstrap from a CVS branch, starting from a given point in time:: 114 114 115 $ tailor .py-b -s cvs -R :pserver:anonymous@server.org:/cvsroot/ \115 $ tailor -b -s cvs -R :pserver:anonymous@server.org:/cvsroot/ \ 116 116 --revision 'unstable-branch 2001-12-25 23:26:48 UTC' \ 117 117 --module something new-darcs-repository … … 121 121 =================== 122 122 123 Should one of the replayed changes generate any conflict, tailor .py123 Should one of the replayed changes generate any conflict, tailor 124 124 will prompt the user to correct them. This is done after the upstream 125 125 patch has been applied and before the final commit on the target … … 235 235 work. With the following command line:: 236 236 237 $ tailor .py--verbose --interactive tailor.cmds237 $ tailor --verbose --interactive tailor.cmds 238 238 Welcome to the Tailor interactive session: you can issue several commands 239 239 with the usual `readline` facilities. With "help" you'll get a list of … … 318 318 ============ 319 319 320 See the output of ``tailor .py-h`` for some further tips. There's320 See the output of ``tailor -h`` for some further tips. There's 321 321 also a `wiki page`_ that may give you some other hints. The 322 322 development of Tailor is mainly driven by user requests at this point,
Note: See TracChangeset
for help on using the changeset viewer.
