On Mon, 28 Jul 2008 17:17:32 +1000 Pigeon <[EMAIL PROTECTED]> wrote: > I just did a few test, but whatever I specified in the git target > "repository", it doesn't seem to be created, used or referenced > anywhere.
Yes, not all backends behaves exactly the same (OTOH, they were written at different times by different hands :-). The GIT one should honor the "repository" option if present, by initially checkout a working copy from there. > > > Exactly. But a git repo consists of a working directory and a "git > > directory". The previous is optional, for example when you store a > > repo on the server, the working directory would just cause > > problems. This is true here as well: the working directory is used > > by tailor, but you should just use the ".git directory" of the > > target repo, you should not care about outside .git, I think. > > Just a clarification, the "working directory" is what specified by > the root-directory setting right? Not always: the "root-directory" sets the place where all the work happens, where tailor will create the subdir(s) containing the source and the target working dirs. If "subdir" is different from ".", the working directory (and possibly its repository as well) will be a *subdirectory* of the "root-directory" place. > > One more question. Once you've cloned the git repository from the > working directory (.git), how should you keep them in sync later when > you do the tailor import again? Do you just treat the tailor working > directory as a remote (origin) and just pull from it? The latter is what I usually do. hth, ciao, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. [EMAIL PROTECTED] | -- Fortunato Depero, 1929. _______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
