On Fri, Aug 25, 2023 at 09:40:19PM +0100, Tixy wrote: > On Fri, 2023-08-25 at 19:47 +0200, john doe wrote: > > On 8/25/23 13:44, Tixy wrote: > > > On Fri, 2023-08-25 at 10:47 +0200, to...@tuxteam.de wrote: > > > > Yes, I think a bare remote is the way to go in this context > > > > > > You can make a repo bare by editing it's config file (.git/config) to > > > have 'bare = true' instead of 'bare = false' under the '[core]' > > > > > > > Generaly, the '.git' extension symbolises a bare repository! > > The opposite is true, the .git directory is the default location for > git's stuff in non-bare repos.
I think that was a misunderstanding: the OP was saying that if the whole repository has a name ending with ".git" (e.g. "foo.git") it is a bare repo, which is, indeed a common convention. What you say is that a non-bare repo contains a subdir called ".git" containing all the git stuff whithin the working dir (and which, by the way, is almost a bare repo itself). Both are true. The OP used this strange term "extension" for the file name ending, which comes from unhappy DOS times ;-) Cheers -- t
signature.asc
Description: PGP signature
