Kean Johnston wrote:
> Is there any problem with mixing and matchign exported and checked
> out trees? I ask before I try because that's easier :)
There is no trouble having upper directories exported and only the
modified directory as a working copy. But it is going to be a bit more
tricky if you want to have an exported subtree inside a normal working
copy. I don't think we really support this.
And exported tree is just a tree, it has nothing to do with a working
copy and nothing will recognise it as such. So what it would look like
to subversion is that you are missing all the .svn directories inside
one subtree, which may or may not work so gracefully. If you manually
mangle the entries file some, I think subversion could be convinced to
"forget" the existence of such a directory - and it might work.
And, there's no way to "update" an exported copy - so I don't think
your developers would like that.
>> And this really doesn't sound trivial to get done. Elimination of
>> text-bases is a nice thing - but the elimination of the need to
>> traverse is what makes it a killer feature. I hope you can come up
>> with a reasonable solution to this.
> How about this. All we need is easy access to the very root of a
> tree. I don't know what functions exist to find it but I am sure
> they must exist, or would be trivial to implement. Once we can, from
> within in WC, get an easy pointer to the root, all we need to do is
> store a simple file in the root's admin directory of files edited.
Yes, that is one way of doing it. But one must take care what happens
when parts of the working copy get moved, updated, removed and
re-added. And 'svn commit' is only one function which needs that
information. Everything, 'svn status', 'svn diff', 'svn revert',
etc. need to have access to that list as well. And the usage ofcourse
differs. For example, 'svn status' should either normally only output
the data for changed files (and not show question marks for unknown
files) or there should be flag for 'svn status' that does that. And
ofcourse 'svn status -v' would force a tree-walk in any case. 'svn
diff' on the other hand should only use the edited information, as
I'm not saying it can't be done, I'm saying it's not trivial. So, I
wish you luck in achieving this.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Dec 17 13:36:08 2002