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

Re: Getting Started

From: Daniel Essin <essin_at_ieee.org>
Date: 2006-12-22 17:37:26 CET

Jean-Marc van Leerdam <j.m.van.leerdam@...> writes:

> Daniel,
> On 22/12/06, Daniel Essin <essin@...> wrote:
> >
> > If I'm in the US and I send a request to China for toys, that's importing.
> > If I
> > go to China and send a request to the US to take some toys off my hands,
> > that's
> > exporting.
> >
> > So tell me again why, in order to import into svn, I go to China (the
> > unmonitored src files) and send a message (the rt-click "import") to svn to
> > take
> > the files off my hands and place them under version control?
> >
> > It would make more sense to me if the import was initiated on the repository
> > directory.
> You have a point in general, but in SVN scope these terms are not used
> as relative terms but as absolute terms.
> Importing means 'bringing something under version control'
> Exporting means 'extracting something that is available under version
> Keep in mind that usually you do not have file access to the
> repository. The repository is a server side thing that gets accessed
> through URLs (http(s):, svn: or file:). In that setting, all SVN
> client commands are executed against local files and/or working
> copies.
Now that I understand it, do you think that it would be reasonable to revise
the GUI so that if you clicked on the repository and selected "import" that the
internal command could be constructed in such a way that it would actually work
instead of throwing an error message and then force you to start over? It's
really just an issue of how the source and destination fields are used to
composed the command.


To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Dec 22 17:38:05 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.