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

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

From: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Mon, 28 Sep 2009 17:17:05 +0100

> -----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,
> 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.

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 :)


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-28 18:18:00 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.