Re: public/private commits

Andrey Dibrov wrote:
[...]
> Branches requires if some part of application or program detaches
> from main development line, and team require to test and build it
> independently to trunk or other branches. Private commits is just
> different feature which doesn't correlate with truck or branches.
> Private commits is just a way to store changes on server instead of
> locally.

You may wish to persist your working copy state in the repository, then.
(This is likely not quite what you're after, but perhaps it's
sufficiently close.)

Assume you're working on project "coolstuff" in working copy
~/svnwc/coolstuff.

$ cd ~/svnwc/coolstuff
$ svn cp . ^/work-in-progress/andrey/coolstuff/2009-09-24_007

-- 
Michael Diers, elego Software Solutions GmbH, http://www.elego.de
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2400180
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].