software:subvesion
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
software:subvesion [2019/12/05 17:24] – [Creating a "stable" tag] rodolico | software:subvesion [2019/12/07 15:02] – rodolico | ||
---|---|---|---|
Line 4: | Line 4: | ||
I sometimes use GUI's on my development workstation. For Linux, the best I've found so far is a very old one named pysvn-workbench, | I sometimes use GUI's on my development workstation. For Linux, the best I've found so far is a very old one named pysvn-workbench, | ||
+ | |||
+ | |||
+ | ==== Configuration File ===== | ||
+ | |||
+ | The configuration for pysvn-workbench is in ~/ | ||
+ | |||
+ | In that directory is also a log file for actions (WorkBench.log) and the most recently used log message (log_message.txt). | ||
+ | |||
+ | The WorkBench.log file appears to be rotated every 100k, ie it will rename the old log file to WorkBench.log.1, | ||
==== Using Templates ==== | ==== Using Templates ==== | ||
Line 31: | Line 40: | ||
- Always work in trunk, unless you're working on a branch. tags is for when you want to create a check point. | - Always work in trunk, unless you're working on a branch. tags is for when you want to create a check point. | ||
- | ===== Creating a " | + | ===== Creating |
+ | <code bash> | ||
+ | svn copy http:// | ||
+ | </ | ||
+ | OR | ||
+ | <code bash> | ||
+ | cd / | ||
+ | svn copy ^/trunk ^/tags/1.0 -m " | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== Maintaining | ||
I've always been intrigued with people who use subversion with a tag that always points to the most recent stable version. Never figured out how they do it, but thanks to one of my associates, came up with this simple action when a new version has become your most recent stable version</ | I've always been intrigued with people who use subversion with a tag that always points to the most recent stable version. Never figured out how they do it, but thanks to one of my associates, came up with this simple action when a new version has become your most recent stable version</ | ||
Line 37: | Line 57: | ||
- Delete the old stable tag if it exists. Be sure and use recursion. | - Delete the old stable tag if it exists. Be sure and use recursion. | ||
- recreate the stable tag from the new version | - recreate the stable tag from the new version | ||
- | |||
- | the URL listed below is one of our projects | ||
<code bash> | <code bash> | ||
svn ls -v ^/tags | svn ls -v ^/tags | ||
- | svn delete http://svn.dailydata.net/svn/ | + | svn delete http://svn.example.com/project/ |
- | svn copy http://svn.dailydata.net/svn/ | + | svn copy http://svn.example.com/project/tags/v1.0 http://svn.example.com/project/ |
</ | </ | ||
Unfortunately, | Unfortunately, | ||
software/subvesion.txt · Last modified: 2020/07/10 22:37 by rodolico