On Thu, Jan 24, 2013, 17:07 John Smith <csos...@gmail.com> wrote: > Some documents write about the .git file, for example > git clone \\[repository server name]\[share name]\example.git >
This notation is somewhat an unwritten(?) standard. The command you cite says: OK Git, go to [repository server name], look for a folder called example.git on the share [share name], assume it is a Git repository (ie. a bare repo or a normal one with a .git folder inside, which is the actual repository), and clone it to my computer to the current working directory, in a folder called example (this last two piece of information is implicit; as you don't tell Git what the destination folder is, it will assume this). (Someone please correct me if I'm wrong, but I think the source folder name can be simply "example", without the ".git" suffix, unless there are both "example" and "example.git" folders present.) So no, you will most probably not find an example.git file/folder in your repository after cloning (unless someone deliberately put it there), that is a directory on the source machine, that contains a Git repository, bare or not. Conventionally, folders with a .git suffix hold a bare repository. The .git "file" is more likely a subdirectory in the cloned stuff (there are exceptions, as others have pointed out). It contains the actual repository, like the full history (again, there can be exceptions, look up “shallow clone”), the branch/tag pointers, etc. > > However I have no .git file in my bare repo. > > -- > > > -- 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. For more options, visit https://groups.google.com/d/optout.
