For human use, a simple "merging tag 2.001" commit message has been fine. Maybe you're thinking of a more complex situation than Jim or I have. In my case, we always merge the tag with the latest version, so looking up the last merge isn't necessary if the tags are sequential. The additional information of which revision number the merge was hasn't ever been needed.
In reply to Re^7: [OT] Best Use of Subversion Branches in Perl Development
by perrin
in thread [OT] Best Use of Subversion Branches in Perl Development
by jkeenan1
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |