[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r33021 - branches/explore-wc/subversion/libsvn_wc

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Thu, 11 Sep 2008 18:10:40 +0100

On Thu, 2008-09-11 at 12:51 -0400, Greg Stein wrote:
> Those are the correct definitions, per wc-by-design.

(I assume you mean, "per 'notes/wc-ng-design'".)

Both of you:

Huh? I was trying to refine the definitions to something more precise
than "ACTUAL is how the working copy really looks." :-)

- Julian

> On Sep 11, 2008, at 12:18, "C. Michael Pilato" <cmpilato_at_collab.net>
> wrote:
>
> > Julian Foad wrote:
> >> On Thu, 2008-09-11 at 08:27 -0700, Greg Stein wrote:
> >>> Thanks for the thoughts.
> >>>
> >>> Note that we need to be able to iterate over all three trees. This
> >>> code just iterates over WORKING, so it won't even have to stat().
> >>> I'll
> >>> need to expand this now to be able to iterate over BASE (no stats)
> >>> and
> >>> over ACTUAL (use readdir), so I can see what those look like.
> >>>
> >>> Now that I think about it, the read_info() needs to be able to
> >>> signal
> >>> an unversioned item when iterating over ACTUAL.
> >>
> >> When we say "WORKING" and "ACTUAL", I'm wondering what exactly we
> >> mean
> >> by each of them.
> >
> > My guess: BASE is what BASE is today. WORKING is how the working
> > copy
> > ought to look given BASE plus the state changes recorded by the
> > working copy
> > library. ACTUAL is how the working copy really looks.
> >
> > $ svn rm file.txt
> > $ touch file.txt
> >
> > BASE has file.txt. WORKING has not. ACTUAL has.
> >
> > If I'm wrong, and if my guess is the same as Julian's, we might need
> > some
> > clearer terms.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-11 19:10:59 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.