On 4/26/2010 11:04 PM, 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.
Thanks
Frank
On Fri, Apr 23, 2010 at 4:19 PM, Curley, John<john.cur...@windriver.com> wrote:
Hi all,
Sounds to me like the developers want to avoid branching and merging.
Try it. You might like it.
Seriously though, if you have concerns with branching and merging, I
suggest some training and make some trial runs in a test repository. I
believe there are software tools that will help you manage the branching
and merging.
HTH,
John
This is exactly what branching and merging are for. Work on a branch to
work out all the kinks in the code, and once satisfied, then you merge
to the trunk to checkin your changes. If your IT dept. doesn't allow
branching, then that's broken, not Subversion....
--
"Dingo" Dave Bartmess
Broomfield, CO. USA
http://edingo.net
