Since the –shared option just sets the permissions on everything in the repository to group-writable you could do this manually later: $ chmod -R g+w the/repo/path Plus, add sharedrepository = 1 under the [core] section in .git/config. Shared repos also have the following receive option defined by default (which you may or may not want): … Read more
For anyone looking to change an existing TortoiseGit installation to use PuTTY rather than OpenSSH, simply right-click, -> TortoiseGit -> Settings -> Network, then change ‘ssh.exe’ to ‘tortoiseplink.exe’. From then on, doing a push/pull should be using Pageant (and any keys you have set up in there) if you also have that running.
You need to git add my_project to stage your new folder. Then git add my_project/* to stage its contents. Then commit what you’ve staged using git commit and finally push your changes back to the source using git push origin master (I’m assuming you wish to push to the master branch).
To verify the object you can use this simply command: git fsck –full git-fsck Verifies the connectivity and validity of the objects in the database fsck – File System ChecK. The name is taken from the Unix fsck command https://git-scm.com/docs/git-fsck If you want you can also verify the pack separately with but you basically dont … Read more
It means that you made a change to filename.cpp, added that change (with git add), then made another change that has not yet been added. The “changes to be committed” part means that Git has updated its index with a change. When you run git commit, the changes to the index will be used to … Read more
Set the config variable merge.ff to false: git config –global merge.ff false (Without –global to limit the effect to the current project)
You can force Git to check the whole repository with git fsck. If a Git repository gets corrupted, you should get a new clone from a non-corrupted repository. Under normal operation Git should check parts of the repository as they are read, so it might take longer to notice some corruption, but it will be … Read more
Here git add * complains, but git add . does what is expected (1.7.0.4, Linux). From git-add(1): The git add command will not add ignored files by default. If any ignored files were explicitly specified on the command line, git add will fail with a list of ignored files. Ignored files reached by directory recursion … Read more
From the SPECIFYING REVISIONS of the git rev-parse man page: A suffix ~<n> to a revision parameter means the commit object that is the <n>th generation grand-parent of the named commit object, following only the first parent. I.e. rev~3 is equivalent to rev^^^ which is equivalent to rev^1^1^1. Consider the examples in the git diff … Read more