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

Re: .SVN folder question

From: Sindbad the Seafarer <sindbad.the.seafarer_at_gmx.net>
Date: 2003-07-20 13:23:40 CEST

Concerning Re: .SVN folder question
Jack Repenning wrote on 19 Jul 2003, 11:47, at least in part:

> At 6:33 PM +0200 7/19/03, Sindbad the Seafarer wrote:
> >Concerning Re: .SVN folder question
> >Ben Collins-Sussman wrote on 19 Jul 2003, 7:13, at least in part:
> > > 1. Try 'svn export'. It's like a checkout, but produces an
> > > unversioned tree (i.e. no .svn/ folders)
> >
> >This would be even worse I suppose: it does not keep the file dates
> >from the working copy but in truth re-creates the files at the
> >destination.
> Ooh! Ooh! Another use-case for preserving commit times on export!
> Sinbad: although "svn export" presently does what you say, we
> recently agreed that it really make the files have the timestamp of
> when they were last checked into SVN. It's turning out to be a
> little harder to do than expected (different operating systems do it
> in different ways), but I think it's still in the plan. So once
> that's done, you'll be able to 'svn export' the while web tree, and
> upload only the changed files, and search engines won't be tricked
> into uploading unchanged files.

Of course the term "export" does not imply that timestamps are
preserved as in "copy". Nevertheless it would perhaps be of general
preferrence, also for the first checkout to a new working copy, to
have the timestamp reflecting the true creation/change time of the
file. I assume that implementating this is a lot easier for exporting
from a wc than from the repository when files are actually created
from the database.

> Also, Ben asked:
> >Why not do what most of us do? Keep the working copy on the web
> >server, and make it the "live" tree served to the world.
> I don't know about Sinbad, but I don't run my own web server (my ISP
> does), and it doesn't have SVN installed. I do run my own SVN repo,
> and do my website maintenance from my own machine, but when I like my
> changes I have to upload them still. (I don't want to serve my
> website through my DSL, nor yet from my pesonal computer).

Things here are the very same (except for DSL not available in the
country side here), the ISP even does not allow telnet (in case that
could ease things, don't have any experience with telnet). However,
now I see my idea of keeping a "live" working copy on the server
updated via svn up would not work with ftp:// for protocol reasons.
When paying for webspace having the admin folders on the server
is not especially desireable anyway. Thus I think till the .SVN
folders are moveable to a central place in either the working copy
or even just on the local disk I'll prefer entering a filter in the FTP
app anytime I want to upload. And since exporting 60+MB any
other day just for an upload of a few changes is also time-
consuming it's not too big an inconvenience compared with the
other options ...

Jan Hendrik

marine niemeyer
jan hendrik niemeyer
- since 1992 -
dorfstrasse 4
27632 padingbuettel / germany
phone / fax +49 (0) 4742-2117
visit our website:

> Jack Repenning
> CollabNet, Inc.
> 8000 Marina Boulevard, Suite 600
> Brisbane, California 94005
> o: 650.228.2562
> c: 408.835-8090

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 20 13:22:34 2003

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.