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

Re: Making import syntax more consistant

From: Benjamin Pflugmann <benjamin-svn-dev_at_pflugmann.de>
Date: 2002-10-16 02:41:06 CEST

Hello.

Just a note..., I would expect a slightly different behaviour.

On Mon 2002-10-14 at 16:12:28 -0700, Peter Davis wrote:
> On Monday 14 October 2002 14:33, Brent Burton wrote:
> > But the results I was expecting (for whatever reason) were
> > along the lines of
> > tar cf - some/long/path | (cd ....; tar xf -)
> > which recreates the some/long/path hierarchy under the .... location.
>
> I'm not sure if this is what you were expecting or not, but just to be clear,
> I don't think import should recreate the tree of the second argument in the
> repository. Expanding on your other example:
>
> $ svn import file:///path/to/repos graphics/bsp
>
> would import ./graphics/bsp/* into the repository root. If you had
> graphics/bsp/readme.txt, it would end up as file:///path/to/repos/readme.txt.

I would expect this to import ./graphics/bsp into the repository root,
-> file://path/to/repos/bsp/readme.txt

I think my expectation is due to cp, mv, rsync, etc. which AFAIK all
work on the named directory if the target is an existing directory and
I think about the repos path as a directory.

I am not sure, if the other way would be a better one. I only wanted
to mention this.

Regards,

        Benjamin.

  • application/pgp-signature attachment: stored
Received on Wed Oct 16 02:41:51 2002

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.