They are yours, to do with as you see fit. Once they're copied out of the commit, they're not Git's files any more.That's why Git must copy them out to ordinary, read/write files. Most programs can't read these files at all. The files that are stored inside each commit are stored in a special, read-only, Git-only, compressed and de-duplicated format.Git initially copies the files that are in some commit out of the commit into your work-tree.The phrase not in the repository here is doing some fairly heavy-duty work. git directory at the top level of your work-tree. The repository is normally contained within the. They are in your working tree or work-tree. The files that you see and work with, when you work inside a Git repository on your computer, are not in the repository. In fact, though, it's simply whichever branch name HEAD in the source repository is attached-to.) They need a term for this because the way they set the recommendation is through their web interfaces. GitHub and other hosting servers call this recommendation the default branch. You choose which new branch name to create, if any, with arguments to your git clone command if you don't choose one, your Git picks a branch to create based on a suggestion made by the other Git, which looks at the source repository. The branch name that gets created here identifies the same commit as some name in the source repository. (At the end of the cloning process, the Git that is doing the cloning normally creates one new branch name in the new repository. This database is not copied, at least not directly, by cloning: the Git that is doing the cloning reads it, but modifies what is to be stored, so that the new clone of some existing repository normally has all the commits but none of the branches. This includes branch names, tag names, remote-tracking names, and other names. The secondary database holds all of the names by which you can find commits. This includes your commits as internal commit objects, along with three other object types that make the commit objects work in the way we expect. The main database, which is copied by cloning, holds all of Git's internal objects. More precisely, a repository consists, at its heart, of two databases: Remember that a repository is not "a bunch of files", it is a collection of commits. Īs you can see from this message, Git is "reinitializing" the existing repository. But in fact you didn't: Reinitialized existing Git repository in.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |