<br><br><div class="gmail_quote">On Jan 22, 2008 5:55 PM, Matthew Fluet <<a href="mailto:fluet@tti-c.org">fluet@tti-c.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br></div>The appropriate place for work-in-progress would be a subversion branch.<br>Our convention has been to make branches with the name<br>"on-YYYYMMDD-NAME-branch". For subversion, you would do something like:
</blockquote><div><br>For smaller changes, where branches are inapopriate, let me turn your attention on the quilt(1) shell script suite:<br><br></div></div><a href="http://savannah.nongnu.org/projects/quilt">http://savannah.nongnu.org/projects/quilt
</a><br><br>Originally concieved by Linux kernel developer Andrew Morton, it is a set of scripts to maintain a stack of patches against sources. Patches can be pushed and popped from the stack as well as ``refreshed'', that is updated with new content. The neat thing is that you can keep on working on a set of changes you wish to do on a source code repository, working up and down the stack and refreshing until things are ready to go into the main repository. The tool is strictly orthogonal to usual Change Management in general.
<br><br>For the emacs users, theres even an .el for emacs to make it easy.<br><br><br>