> > To resolve the problem, I did a local clone of the repo but each
> > clone consumes nearly 2-3GB of space. Is there an efficient way that
> > uses less space (i.e reduce the need for clones) and reduces the need
> > to rebuild every time I switch between branches.
> This sounds more like a problem with your build system.
> Can you put build artifacts in a release-dependent sub-directory?
> That might fix is all with a single repository and would be an approach I 
> would consider.

Another possibility is to use multiple work trees with a single
repository; the git-new-workdir script in git's contrib directory
helps set that up.  It works by creating a .git directory with
symlinks back to the original.  You just have to be careful not to
modify a branch in one work tree that's also checked out in another.
(Easiest to avoid this by just not ever checking out the same branch



You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to