Question

Some of my current code files have a few lines changed for test purposes (a different constant value or some commented-out line). It doesn't seem like something I should commit as it's not a proper change to the code, just temporary. Yet, the files keep showing up as changed when checking for changes (quite normal!)

This wouldn't be so bad if they never changed otherwise (I could use a changeset), but a few times now, I've had to change these files for other reasons, with stuff that I want to commit.

I do know about Restore After Commit and this is not a question about how to commit partial files. My issue is that since the files show up as changed all the time, I never notice when they finally contain some pertinent change.

Any trick to keep the files out of the way until they contain pertinent changes?

I was thinking something like "ignore these changes", where SVN would only show the file as changed if they contained changes other than the initial set of changes. Some sort of... local temporary commit, if that makes sense?

Was it helpful?

Solution

Some sort of... local temporary commit

Subversion is not DVCS, you can't have anything locally stored. But you can commit your temporary changes into (semi-private) branch and return to work with trunk's version (removing branch-specific changes)

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top