RE: How do I manage temporary source code hacks with subversion?

> -----Original Message-----
> From: Jonty [mailto:subversion_at_jonmail.co.uk]
> Sent: Monday, September 28, 2009 2:43 PM
> To: users_at_subversion.tigris.org
> Subject: How do I manage temporary source code hacks with subversion?
>
> Hi,
>
[snip]
>
> 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.
>

I'd say the best solution you have here is to use changelists.
http://blogs.open.collab.net/svn/2007/07/one-quality-of-.html

they're not the perfect solution for you, but might get you closer to
what you want.

Alternatively, you can add a property to a file, and list them, so you
can mark files as you want. I'm not sure this solves your problem fully
either, but there are 2 items for you to investigate further.

Personally, I stick TODO: markers in my code too. Some of them are still
there :)

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2401301

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