"Rui, Guo" <timmyguo_at_mail.ustc.edu.cn> writes:
>> I'm not sure exactly what you meant. Could you give an example?
>
> Take the greek tree as an example. Consider a wc with directory A at
> immediates and revision 1. And somebody introduced items A/D/new1 and
> A/B/E/new_tree at revision 2. When we update our wc from revision 1 to 2, we
> will notice the skipped new item A/D/new1 but not the A/B/E/new_tree. The idea
> is that, if we include a directory in wc (a leaf directory in wc), we should
> be able to see what happens (piratical) to it and probably would like to. If
> we didn't bother to include the directory in wc, we are probably not
> interested at all.
>
> In such a way, the server do not need to crawl into unrelated path and thus
> maintains the current way it works. The only extension is that the server will
> have to feedback a little more when handling leaf directories in wc. However,
> this behavior should be explicitly requested by client and should be still
> considered 'finely-tuned directory delta'.
>
> Did I make it clear enough?
Hmmm. Almost -- I understand more now.
A good way to describe a change like this is to simply write the new
documentation string(s) for any functions that will be affected. That
is the final specification anyway, and if the reviewers can't understand
the new doc strings, then future readers won't either :-). So if you
write them before making the code change, then we can tell exactly what
will happen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-29 17:49:31 CEST