On Thu, 10 Mar 2016 21:56:07 +0100 Pablo Rodríguez <[email protected]> wrote:
[...] > As far as I know, all my repos are normal. I don’t know how to get > non-bare repositories (no idea of what these might be). [...] A bare repository is a repository with no work tree -- which contains the files currently checked out -- and the index (the staging area). A normal (also: "regular", "non-bare") repository consists of a work tree and a subdirectory named ".git" in it which contains the local repository's data. A bare repository has no work tree and no index. That is, the directory with a bare repository contains the repository's data right at the top level. (Because of this, it's customary to attach the suffix ".git" to the names of directories of bare repositories.) Bare repositories are hardly usable for performing "regular" tasks of recording commits in them and are mostly used for "server-side" repositories which everyone pushes their stuff into and fetches others' stuff from. To give an example, all repos in public Git hostings (such as Bitbucket, Github etc) are bare. A number of "casual" tasks can still be performed in bare repositories. Say, you can enumerate/create/delete/reset branches in them, inspect their history, manipulate configuration etc. With advanced commands, it's possible to fetch files of particular commits from such repos, which is commonly used for, say, website deployments. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
