<p>+1 for switching to git or hg, but you still put those patches in the release, then (as often as you like) merge from release to trunk. Tags are on a specific SHA1 so they never move (but you don't want them to).</p>
<div class="gmail_quote">On Apr 5, 2012 11:14 AM, "James Porter" <<a href="mailto:jvporter@wisc.edu">jvporter@wisc.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, 2012-03-28 at 12:59 -0500, Tim Tautges wrote:<br>
> What I really should have done was add this to the 4.5 branch, rather than the tagged code. I'll back out that change<br>
> and put it in the branch where it belongs.<br>
<br>
This is one of the (many) bad things about SVN: it doesn't actually<br>
support tagging, except by convention. Some day, I think it might be<br>
useful to look into Git or Mercurial, since - among other niceties -<br>
they actually have a concept of "tags".<br>
<br>
- Jim<br>
<br>
</blockquote></div>