Pro Git 2nd Edition 2.1.413less of a difference. If you do want to install Git from source, you need to have the following libraries that Git depends on: autotools, curl, zlib, openssl, expat, and libiconv. For example, if you’re push command doesn’t transfer tags to remote servers. You will have to explicitly push tags to a shared server after you have created them. This process is just like sharing remote branches — you can able to share your branches by pushing them to a shared server, working with others on shared branches and rebasing your branches before they are shared. Next, we’ll cover what you’ll need to run your0 码力 | 731 页 | 21.49 MB | 1 年前3
Pro Git 2nd Edition 2.1.413less of a difference. If you do want to install Git from source, you need to have the following libraries that Git depends on: autotools, curl, zlib, openssl, expat, and libiconv. For example, if you’re push command doesn’t transfer tags to remote servers. You will have to explicitly push tags to a shared server after you have created them. This process is just like sharing remote branches — you can able to share your branches by pushing them to a shared server, working with others on shared branches and rebasing your branches before they are shared. Next, we’ll cover what you’ll need to run your0 码力 | 501 页 | 17.96 MB | 1 年前3
Pro Git 2nd Edition 2.1.413 less of a difference. If you do want to install Git from source, you need to have the following libraries that Git depends on: autotools, curl, zlib, openssl, expat, and libiconv. For example, if you’re push command doesn’t transfer tags to remote servers. You will have to explicitly push tags to a shared server after you have created them. This process is just like sharing remote branches — you can able to share your branches by pushing them to a shared server, working with others on shared branches and rebasing your branches before they are shared. Next, we’ll cover what you’ll need to run your0 码力 | 691 页 | 13.35 MB | 1 年前3
Pro Git 中文版 第2版 2.1.66如果到该项目目录中运行 git init 命令,并加上 --shared 选项, 那么 Git 会自动修改该仓库目录的组权限 为可写。 注意,运行此命令的工程中不会摧毁任何提交、引用等内容。 $ ssh user@git.example.com $ cd /srv/git/my_project.git $ git init --bare --shared 由此可见,根据现有的 Git 仓库创建一个裸仓库,然后把它放上你和协作者都有 git-credential-read-only,放到我们的 PATH 路径下并且给予执行权限。 一 个交互式会话类似: 333 $ git credential-read-only --file=/mnt/shared/creds get protocol=https host=mygithost protocol=https host=mygithost username=bob password=s3cre7 由于这个的名字是 “git-” 开头,所以我们可以在配置值中使用简便的语法: $ git config --global credential.helper 'read-only --file /mnt/shared/creds' 正如你看到的,扩展这个系统是相当简单的,并且可以为你和你的团队解决一些常见问题。 总结 你已经接触了很多能够精确地操控提交和暂存区的高级工具。 当你碰到问题时,你应该可以很容易找出是哪个0 码力 | 501 页 | 19.30 MB | 1 年前3
Pro Git 中文版 第2版 2.1.66如果到该项目目录中运行 git init 命令,并加上 --shared 选项, 那么 Git 会自动修改该仓库目录的组权限为可写。 注意,运行此命令的工程中不会摧 毁任何提交、引用等内容。 $ ssh user@git.example.com $ cd /srv/git/my_project.git $ git init --bare --shared 由此可见,根据现有的 Git 仓库创建一个裸仓库,然后把它放上你和协作者都 git-credential-read-only,放到我们的 PATH 路 径下并且给予执行权限。 一个交互式会话类似: $ git credential-read-only --file=/mnt/shared/creds get protocol=https host=mygithost protocol=https host=mygithost username=bob password=s3cre7 由于这个的名字是 “git-” 开头,所以我们可以在配置值中使用简便的语法: $ git config --global credential.helper 'read-only --file /mnt/shared/creds' 正如你看到的,扩展这个系统是相当简单的,并且可以为你和你的团队解决一 些常见问题。 总结 你已经接触了很多能够精确地操控提交和暂存区的高级工具。 当你碰到问题 时,你应0 码力 | 670 页 | 13.59 MB | 1 年前3
共 5 条
- 1













