Re: wc-ng base/working nodes in a copied tree

Excluded in the wc is just that. It does not mean "delete upon commit." We
have other statii to mean that.

Imagine a local-copy of a large tree, simul with excluding a large portion
so that u don't have to keep/copy as much locally. That doesn't mean
"delete". It is simply an organizational mechanism.

On Apr 7, 2010 5:44 AM, "Philip Martin" <philip.martin_at_wandisco.com> wrote:

Greg Stein <gstein_at_gmail.com> writes:

> > Another problem is a copy of a mixed revision tree that includes base
> > nodes that are not-pre...

> on phone, so this will be terse, but wanted you to consider: I'd thought
> about the copy-of-not-p...
If the source has both excluded and not-present nodes, do we need to
distinguish them in the copy? Would we delete all the excluded nodes
in the copy when committing? There was a thread a few months ago
where a user reported that a wc-to-repo copy of a sparse working copy
didn't result in a sparse copy and asked if this was a bug; we didn't
really reach a consensus about what would be the correct behaviour.

--
Philip