On Sun, Dec 04, 2022 at 08:03:12AM +0100, Uwe Brauer wrote: > > Exactly - that's how I've been operating for a long time and I've never had > > any problems - everything has always worked correctly and I have the added > > security of a copy on the network + history on OneDrive, as if something > > were to happen. Full security. > > It just occurred to me: > > Mercurial has the *share* extension, > > which allows to, well, share repositories over directories. (Not sure > how safe that would be in our scenario) > > I think git has worktree, although I am not sure whether it is 100 % > equivalent.
Well, Git calls "the work tree" a directory to which the current commit (at which HEAD points) is checked out. Hence a worktree is the directory in which the ".git" subdirectory sits, and where you tinker with the files to record a new commit. Git also has a command, `git worktree`, which allows attaching another work tree to the existing local Git repository - that ".git" subdirectory or a normal Git repository, or to a bare repository, which has no work tree. A way to share stuff with Git using "sneakernet" is `git bundle`: it creates a single file which can contain normal Git "objects" such as commits, tags etc. Normal Git commands can fetch/pull from a bundle file and push to it. Sure, there also exists `git archive`, but it's for archiving a set of files contained in a particular single commit, so it's a tool mostly to create downloadable releases of a pieces of software. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/20221204122658.ywt4qiy6yx7gvmhy%40carbon.
