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

What's the best practice to track local modifications?

From: Liu Yubao <yubao.liu_at_gmail.com>
Date: 2006-08-08 05:45:09 CEST

Our administrator doesn't allow us to create private branches
on public repos, and I want to track my local modifications,
so I can roll back to old state. I wouldn't like to create
patches regularly because it's difficult to manage many patches.

I can use another VC tool(CVS + TortoiseCVS ?), but it's not
convenient to use two VC tool at the same time.

I can create a private SVN repos, but I wouldn't like to have
two working copies because this means I need four times disk space
to store my source tree.

It seems a distributed VC tool fits me, but
1) I don't find a mature and user friendly (eg, with GUI) free
distributed VC tool for windows,
2) I wouldn't like to use two VC tools at the same time, almost
each VC tool introduces a new methodology:-)

Then, what's the best practice to track local modifications?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 8 05:46:19 2006

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.