little work, you can commit happily (to your local copy, remember?) until you get to a network connection to upload. If you go home and can’t get your VPN client working properly, you can still work. -s : $ sudo chsh git -s $(which git-shell) Now, the git user can still use the SSH connection to push and pull Git repositories but can’t shell onto the machine. If you try, you’ll see a login shell is not enabled. hint: ~/git-shell-commands should exist and have read and execute access. Connection to gitserver closed. At this point, users are still able to use SSH port forwarding to access

little work, you can commit happily (to your local copy, remember?) until you get to a network connection to upload. If you go home and can’t get your VPN client working properly, you can still work. -s : $ sudo chsh git -s $(which git-shell) Now, the git user can still use the SSH connection to push and pull Git repositories but can’t shell onto the machine. If you try, you’ll see a login shell is not enabled. hint: ~/git-shell-commands should exist and have read and execute access. Connection to gitserver closed. At this point, users are still able to use SSH port forwarding to access

little work, you can commit happily (to your local copy, remember?) until you get to a network connection to upload. If you go home and can’t get your VPN client working properly, you can still work. -s : $ sudo chsh git -s $(which git-shell) Now, the git user can still use the SSH connection to push and pull Git repositories but can’t shell onto the machine. If you try, you’ll see a shell is not enabled. hint: ~/git-shell-commands should exist and have read and execute access. Connection to gitserver closed. At this point, users are still able to use SSH port forwarding to access

shell is not enabled. hint: ~/git-shell-commands should exist and have read and execute access. Connection to gitserver closed. 此时，用户仍可通过 SSH 端口转发来访问任何可达的 git 服务器。 如果你想要避免它，可编辑 authorized_keys 文件并在所有想要限制的公钥之前添加以下选项： log $ git diff Submodule DbConnector c3f01dc..d0354fc: > more efficient db routine > better connection routine 如果在此时提交，那么你会将子模块锁定为其他人更新时的新代码。 如果你不想在子目录中手动抓取与合并，那么还有种更容易的方式。 运行 git submodule update non-null terminated lines > more robust error handling > more efficient db routine > better connection routine 这非常有趣，因为我们可以直接看到将要提交到子模块中的提交日志。 提交之后，你也可以运行 git log -p 查看这个信息。 $ git log -p --submodule

shell is not enabled. hint: ~/git-shell-commands should exist and have read and execute access. Connection to gitserver closed. 此时，用户仍可通过 SSH 端口转发来访问任何可达的 git 服务器。 如果你想 要避免它，可编辑 authorized_keys 文件并在所有想要限制的公钥之前添加以 log $ git diff Submodule DbConnector c3f01dc..d0354fc: > more efficient db routine > better connection routine 如果在此时提交，那么你会将子模块锁定为其他人更新时的新代码。 如果你不想在子目录中手动抓取与合并，那么还有种更容易的方式。 运行 git submodule update non-null terminated lines > more robust error handling > more efficient db routine > better connection routine 这非常有趣，因为我们可以直接看到将要提交到子模块中的提交日志。 提交 之后，你也可以运行 git log -p 查看这个信息。 $ git log -p --submodule