Re: Self-inflicted "abort" in a newbie attempt at read-only exploration of a cloned repository?

On 06/04/18 07:56 PM, Jeff King wrote: On Thu, Apr 05, 2018 at 04:18:23PM -0700, Bryan Turner wrote: The documentation for --work-tree says: --work-tree= Set the path to the working tree. It can be an absolute path or a path relative to the current working directory. This can also be

Self-inflicted "abort" in a newbie attempt at read-only exploration of a cloned repository?

hat begins with my stated goal of an extract-only usage of cloned GIT repositories? (Maybe the root cause is my reluctance to learn the more involved GIT usages.) Does the above reproducible abort deserve attention? Any suggestion for my stated goal? Thanks in advance, - Thierry Moreau

Re: Self-inflicted "abort" in a newbie attempt at read-only exploration of a cloned repository?

On 05/04/18 11:34 PM, Bryan Turner wrote: On Thu, Apr 5, 2018 at 4:18 PM, Bryan Turner wrote: So passing --work-tree tells Git where to store your _files_, but it's still using the same .git directory. If your goal is to have worktrees for various versions, that