Nicolas Williams wrote:
On Thu, Oct 05, 2006 at 05:25:17PM -0700, David Dyer-Bennet wrote:
No, any sane VC protocol must specifically forbid the checkin of the
stuff I want versioning (or file copies or whatever) for. It's
partial changes, probably doesn't compile, nearly certainly doesn't
work. This level of work product *cannot* be committed to the
repository.
[...]
One of the big problems with CVS and SVN and Microsoft SourceSafe is
that you don't have the benefits of version control most of the time,
because all commits are *public*.
I think what you're saying is something like this: a VC repository is
one thing, but when I'm working on something not ready to put into that
repository I still want versioning in my "workspace."
That's still VC though!
This is just one class of problem that I think VC might be useful for.
We could go on, specific case by case coming up with best practices for
applications, but it seems to me that FV is trying to solve a general
problem in general way. Whether that is a good idea or bad idea I don't
know.
However would it be great if I could somehow easily FV a file I am
working on with some arbitrary (closed) application I am forced to use
without the application really knowing about it, and with little or no
actions I have to take to do so?
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
