[GitHub] [arrow] cyb70289 commented on pull request #7541: ARROW-9224: [Dev][Archery] Copy local repo on clone failure

[GitBox <gi...@apache.org>]

cyb70289 commented on pull request #7541:
URL: https://github.com/apache/arrow/pull/7541#issuecomment-649595034


   > Can you try using `git clone --shared` instead? It should avoid the copy.
   
   `--shard` works okay per my test. What about simply replacing `git clone --local` with `git clone --shared`?
   From man page, the only **danger** of `--shared` is if I delete and prune the test branch when related test is running, looks not real.
   
   ```
          --shared, -s
              When the repository to clone is on the local machine, instead of using hard links, automatically setup .git/objects/info/alternates to share the
              objects with the source repository. The resulting repository starts out without any object of its own.
   
              NOTE: this is a possibly dangerous operation; do not use it unless you understand what it does. If you clone your repository using this option
              and then delete branches (or use any other Git command that makes any existing commit unreferenced) in the source repository, some objects may
              become unreferenced (or dangling). These objects may be removed by normal Git operations (such as git commit) which automatically call git gc
              --auto. (See git-gc(1).) If these objects are removed and were referenced by the cloned repository, then the cloned repository will become
              corrupt.
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org