[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

How do I manage temporary source code hacks with subversion?

From: Jonty <subversion_at_jonmail.co.uk>
Date: Mon, 28 Sep 2009 14:43:23 +0100


I am developing an application with the source code stored in
subversion. Occasionally I need to hack some part of the source with
code that I know is bad, but I need the hack so I can get on with
developing the rest of the application.

How can I use subversion to track all the hacks in the source? I want
to make sure that I go back and rework those bad pieces of code before I
release the application. Is there a tool in subversion that will mark a
piece of code as a hack, remember the mark, and then let me list off all
the hacks that are still in the source?

An example might make the question clear. Let's say I am writing two
functions, A and B. Both A and B are complicated and each one will
take several days to write. To make things worse they are mutually
recursive: A calls B in some conditions and B calls A in some

I set of coding function A. I reach the point where I need to call B
but I don't want to break off and write the whole thing. I write a
small function called B that returns a fixed value. This is a hack,
but I need it so I can carry on coding A.

I want to commit the source to subversion but I also need to mark
the code for function B as a hack. Later when I write the correct
code for B and commit it I want the mark removed. And to keep track
of where I am I need a tool that can list all the marks.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-28 15:46:58 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.