On Wed, 02 Aug 2006, Garrett Rooney wrote:
> On 8/2/06, Daniel Rall <dlr@collab.net> wrote:
>
> >> Would it be acceptable in a wc to wc copy?
> >
> >Good question. This is probably a (rather significant) change in
> >behavior for what I assume was previously a disconnected operation.
> >
> >Anyone else have thoughts on this?
>
> Why should we need to do that? The version in the working copy should
> already have the needed info in its mergeinfo property, right? It
> seems like we should be keeping enough cached info to make contacting
> the server in such cases unnecessary...
No, the merge info for the "copy destination" path in the WC won't
include the (history traced) list of revisions from when it first
appeared at that path until "now" unless we contact the repository.
In fact, the path is likely to include only merge info from local
modifications (e.g. merges), as most revisions will (hopefully) have
been elided into its parent directory.
- application/pgp-signature attachment: stored
Received on Thu Aug 3 01:17:38 2006