So now all you need is an easy way to identify the who, what, and when of the files you are examining. which files you want to examine) and you know when (both by date and by revision number by cross-referencing the release M.N tag with revision history). You believe that this defect showed up only in the last month and seems tied to the minor release that was the result of adding features X and Y worked on by developers A, B, and C. Say you are trying to track down a defect and need to review a collection of files as you probe the system, test hypotheses, and follow your hunches. Reminder: Refer to the Subversion book and the TortoiseSVN book for further reading as needed, and as directed in the recipes below. This installment examines the less well-known but extremely handy world of embedded version information. Part 4: Sharing source-controlled libraries in other source-controlled projects.Part 3: Putting things in and taking things out of source control.Part 2: Adding, deleting, moving, and renaming files, plus filtering what you add.Part 1: Checkouts and commits in a multiple-user environment.This is the fifth installment of the TortoiseSVN and Subversion Cookbook series, a collection of practical recipes to help you navigate through the occasionally subtle complexities of source control with Subversion and its ubiquitous GUI front-end, TortoiseSVN. Troubleshooting why keyword expansion fails.Keeping your keyword expansions to fixed widths.Automatically enabling keyword expansion in new files. Inserting the author, the revision, or other keywords when committing. Enabling keyword substitution in a file.You may be bypassing such things as email notifications of the change, or backup systems that keep track of revision properties.TortoiseSVN and Subversion Cookbook Part 5: Instrumenting Files with Version Information - Simple Talk Skip to content However, if you decide to use this option, be very careful. If the "pre-revprop-change" hook is not in place (or you want to bypass the hook script for some reason), you can also use the -bypass-hooks option. Where REPOS_PATH is the repository location, N is the revision number whose log message you wish to change, and FILE is a file containing the new log message. You cannot modify a remote repository using this command. This must be done by referring to the repository's location on the filesystem. If you run this command from within a working copy, you can leave off the URL. Where N is the revision number whose log message you wish to change, and URL is the location of the repository. $svn propset -r N -revprop svn:log "new log message" URL Once revision property modifications are enabled, you can change a revision's log message by passing the -revprop switch to svn propedit or svn propset, like either one of these: $svn propedit -r N -revprop svn:log URL The "pre-revprop-change" hook has access to the old log message before it is changed, so it can preserve it in some way (for example, by sending an email). This is done by creating a hook called "pre-revprop-change". Method 1: Enable Revision Property Modifications However, there are a couple of ways to get Subversion to change a revision property. That is because changes to revision properties (like svn:log) cause the property's previous value to be permanently discarded, and Subversion tries to prevent you from doing this accidentally. By default, the log message property (svn:log) cannot be edited once it is committed. Log messages are kept in the repository as properties attached to each revision.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |