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

Re: more test suite code

From: Sam TH <sam_at_uchicago.edu>
Date: 2001-04-20 14:21:48 CEST

On Fri, Apr 20, 2001 at 07:02:12AM -0500, Ben Collins-Sussman wrote:
> Sam TH <sam@uchicago.edu> writes:
>
> > Also, could someone please look at some of the code I've written and
> > let me know if I'm remotely on the right track? Thanks.
>
> I'll definitely look at this stuff today... I've been really swamped.
>

Cool. I should have entries hash -> tree done soon too.

> > Finally, could someone explain what the heck the output of "svn
> > import" actually represents?
>
> It's the same output as a commit. What's confusing?
>
> Each line has the word {Changing | Adding | Deleting } followed by a
> path to a dir or file. The very last line is "Commit succeeded."
>
> In xml_tests.py right now, I'm checking the last line by hand, popping
> it off the output list, and then doing a regular old compare_sets().
>
> It's just a variant of the output you get from checkout or update.

Ok, here's what I said in the email I referenced:

> [sam_at_samth cs-compile]$ export REPOS=file:///home/sam/repos/
> [sam@samth cs-compile]$ svn import $REPOS old-flame/ flame

> Now, from the interface of import, and my experience with CVS, I would
> expect this to do one of the two following things:

> 1. Create a dir in the repository called old-flame, with an inital tag
> of flame and the contents of old-flame.
> 2. Create a dir in the repository called flame, the contents of
> old-flame.

> But, this command produces lots of messages like so:

> [snip]
> Adding old-flame//flame/tests/identifier.exp
> Adding old-flame//flame/tests/keywords.exp
> Adding old-flame//flame/tests/numbers.exp
> Adding old-flame//flame/tests/quick.exp
> [snip]

> This suggests that a directory in the repository is being created,
> called old-flame, with a subdir called flame, with that subdir having
> the contents of old-flame. That seems really strange and
> counter-intuitive. Fortunately, that isn't what actually happens, as
> we soon see.

Maybe I'm missing something about the structure of the repository, but
this was really confusing. Especially given that 'svn co' give
different paths (no old-flame).

I want to build a tree out of this, which should be rooted at some
arbitrarily named dir. Since the working copy that checking this out
results in looks like this:

        flame/tests/*
        flame/other/*
        flame/*

and so on, I think that the unnamed root node should correspond to
'flame'. That really just means stripping off the first part of that
output, but that seems weird.

Am I missing something?

           
sam th --- sam_at_uchicago.edu --- http://www.abisource.com/~sam/
OpenPGP Key: CABD33FC --- http://samth.dyndns.org/key
DeCSS: http://samth.dyndns.org/decss

  • application/pgp-signature attachment: stored
Received on Sat Oct 21 14:36:29 2006

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