Greg Hudson wrote:
>Although I imagine seversal classes of users would find a use for this
>feature, I think it would make libsvn_wc even more hackish than it
>already is, and would generally complicate Subversion more than it's
>worth.
>
>But maybe there's a more general and more elegant solution. I'll
>observe that people may want to have local changes to file contents, as
>well as properties, without having them committed. So maybe what we
>want is some kind of "commit mask" which you can drop into a working
>copy (not sure how--a specially named file, a file in .svn, a directory
>property) to prevent specific changes from being committed. Then only
>the commit subsystem needs to be affected, not the entirety of
>libsvn_wc.
>
>
This whole thread seems to be moving towards reinventing two-stage
commits, where changes (and commits) stay local by default until
explicitly promoted to the (a) repository. Svk does something like that,
I believe (and so do BitKeeper and AccuRev, for example). I'm fairly
sure this is an option we'd want to have in 2.0, along wit the famous
libsvn_wc rewrite; in fact I envision stealing the design from svk, if
possible.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 4 12:30:59 2004