frank wang wrote:
Thanks for all reply.
I like the subversion since it is a nice tool running both on window
and linux. I looked git and svk and it seems they are only running on
linux and I am uisng windowXP. I really hope that svk can become more
stable and mature and runs on window.
Anyway, here is reason I want to check in the code into a private
resository before I merge the code into the office SVN. During the
development, I added a lot of codes for debugging in many stages. I
want to keep track these changes during the development, so if
anything does not work, then I can easily trace back to find a working
version. All these debugged codes are not supposed to be checked in to
the official SVN. After all debugging steps, I will clean the code and
test it. Once it is working, then the final code will be checked into
the official SVN. By doing this, I can add debug code, print out the
results and will not worry that later I lost track if something I
added break the code.
What you describe here is exactly the scenario where most places would use a
branch in the one-and-only subversion repository. Branches don't affect
anything else until you merge into the trunk - or wherever the code destined for
release is. There are some rare legitimate reasons to avoid working this way -
like not having network connectivity or temporarily testing with components that
others using the repository would not be allowed to see. But this sounds like
you or whoever manages the repository just doesn't want to use subversion the
way it is designed - and there's not a good alternative.
--
Les Mikesell
lesmikes...@gmail.com
