diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawmhfodZquCI_EEl-f3h7HkROTszlsQL6yA <Joe@web> | 2013-06-15 12:48:17 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-06-15 12:48:17 +0000 |
| commit | 3f4483e285aa7eb231031065a24e747a4b46d29d (patch) | |
| tree | a0823d47e45690d5ce1764e20592197dcf2e8ca1 | |
| parent | 7448e6ff765ae68984e73ec0f596f9c9934e26ac (diff) | |
| -rw-r--r-- | doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_.mdwn | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_.mdwn b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_.mdwn index b90162d89..84f7717b5 100644 --- a/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_.mdwn +++ b/doc/bugs/windows_port_-_repo_can__39__t_pull_newly_added_files_.mdwn @@ -2,7 +2,7 @@ Using a centralized remote repository, new files that are added to the repository after it's pulled cannot be directly accessed - instead are pulled as symlinks. -The workaround is to create a remote repository that clones from the source. That repo can pull all files correctly +The workaround is to create a new remote repository that clones from the source. That repo can pull all files correctly ### What steps will reproduce the problem? @@ -10,6 +10,7 @@ The following script works fine when everything is run on a linux box. If the sa a file, testrepo.sh is set up on the server to simplify the creation of the repo for testing +**testrepo.sh** [[!format sh """ rm -rf repo.git @@ -21,6 +22,7 @@ git annex sync """]] +**test script** [[!format sh """ ssh joebo@xxxxx sh testrepo.sh |