 Pro Git 2nd Edition 2.1.413commit checksum stored in a file — no other information is kept. To create a lightweight tag, don’t supply any of the -a, -s, or -m options, just provide a tag name: $ git tag v1.4-lw $ git tag v0.1 v1 your history their work is based; a proper three-way merge is the default rather than having to supply a -3 and hope the patch was generated off a public commit to which you have access. If you aren’t want to change the last three commit messages, or any of the commit messages in that group, you supply as an argument to git rebase -i the parent of the last commit you want to edit, which is HEAD~2^0 码力 | 731 页 | 21.49 MB | 1 年前3 Pro Git 2nd Edition 2.1.413commit checksum stored in a file — no other information is kept. To create a lightweight tag, don’t supply any of the -a, -s, or -m options, just provide a tag name: $ git tag v1.4-lw $ git tag v0.1 v1 your history their work is based; a proper three-way merge is the default rather than having to supply a -3 and hope the patch was generated off a public commit to which you have access. If you aren’t want to change the last three commit messages, or any of the commit messages in that group, you supply as an argument to git rebase -i the parent of the last commit you want to edit, which is HEAD~2^0 码力 | 731 页 | 21.49 MB | 1 年前3
 Pro Git 2nd Edition 2.1.413commit checksum stored in a file — no other information is kept. To create a lightweight tag, don’t supply any of the -a, -s, or -m options, just provide a tag name: $ git tag v1.4-lw $ git tag v0.1 v1 your history their work is based; a proper three-way merge is the default rather than having to supply a -3 and hope the patch was generated off a public commit to which you have access. If you aren’t want to change the last three commit messages, or any of the commit messages in that group, you supply as an argument to git rebase -i the parent of the last commit you want to edit, which is HEAD~2^0 码力 | 501 页 | 17.96 MB | 1 年前3 Pro Git 2nd Edition 2.1.413commit checksum stored in a file — no other information is kept. To create a lightweight tag, don’t supply any of the -a, -s, or -m options, just provide a tag name: $ git tag v1.4-lw $ git tag v0.1 v1 your history their work is based; a proper three-way merge is the default rather than having to supply a -3 and hope the patch was generated off a public commit to which you have access. If you aren’t want to change the last three commit messages, or any of the commit messages in that group, you supply as an argument to git rebase -i the parent of the last commit you want to edit, which is HEAD~2^0 码力 | 501 页 | 17.96 MB | 1 年前3
 Pro Git 2nd Edition 2.1.413 commit checksum stored in a file — no other information is kept. To create a lightweight tag, don’t supply any of the -a, -s, or -m options, just provide a tag name: $ git tag v1.4-lw $ git tag v0.1 v1 your history their work is based; a proper three-way merge is the default rather than having to supply a -3 and hope the patch was generated off a public commit to which you have access. If you aren’t want to change the last three commit messages, or any of the commit messages in that group, you supply as an argument to git rebase -i the parent of the last commit you want to edit, which is HEAD~2^0 码力 | 691 页 | 13.35 MB | 1 年前3 Pro Git 2nd Edition 2.1.413 commit checksum stored in a file — no other information is kept. To create a lightweight tag, don’t supply any of the -a, -s, or -m options, just provide a tag name: $ git tag v1.4-lw $ git tag v0.1 v1 your history their work is based; a proper three-way merge is the default rather than having to supply a -3 and hope the patch was generated off a public commit to which you have access. If you aren’t want to change the last three commit messages, or any of the commit messages in that group, you supply as an argument to git rebase -i the parent of the last commit you want to edit, which is HEAD~2^0 码力 | 691 页 | 13.35 MB | 1 年前3
 Gitea v1.21.1 中文文档bantime = 900 8. action = iptables-allports 如果你的 Gitea 实例运行在 Docker 容器中,并且直接将容器端口暴露到外部网络, 你还需要添加 chain="FORWARD" 到监狱规则配置文件 /etc/fail2ban/jail.d/gitea-docker.conf 以适应 Docker 的网络转发规 则。但如果你在容器的宿主机上使用 本文档使用 书栈网 · BookStack.CN 构建 6. findtime = 3600 7. bantime = 900 8. action = iptables-allports[chain="FORWARD"] 最后,运行 systemctl restart fail2ban 即可应用更改。现在,你可以使用 systemctl status fail2ban 检查 fail2ban0 码力 | 303 页 | 3.88 MB | 1 年前3 Gitea v1.21.1 中文文档bantime = 900 8. action = iptables-allports 如果你的 Gitea 实例运行在 Docker 容器中,并且直接将容器端口暴露到外部网络, 你还需要添加 chain="FORWARD" 到监狱规则配置文件 /etc/fail2ban/jail.d/gitea-docker.conf 以适应 Docker 的网络转发规 则。但如果你在容器的宿主机上使用 本文档使用 书栈网 · BookStack.CN 构建 6. findtime = 3600 7. bantime = 900 8. action = iptables-allports[chain="FORWARD"] 最后,运行 systemctl restart fail2ban 即可应用更改。现在,你可以使用 systemctl status fail2ban 检查 fail2ban0 码力 | 303 页 | 3.88 MB | 1 年前3
 Pro Git 中文版 第2版 2.1.66e372b945b6e884e 1f7a7a472abf3dd9643fd615f6da379c4acb3e3a blob 10 19 7282 non delta: 15 objects chain length = 1: 3 objects .git/objects/pack/pack-978e03944f5c581011e6998cd0e9e30000905586.pack: ok 此处,033b40 码力 | 501 页 | 19.30 MB | 1 年前3 Pro Git 中文版 第2版 2.1.66e372b945b6e884e 1f7a7a472abf3dd9643fd615f6da379c4acb3e3a blob 10 19 7282 non delta: 15 objects chain length = 1: 3 objects .git/objects/pack/pack-978e03944f5c581011e6998cd0e9e30000905586.pack: ok 此处,033b40 码力 | 501 页 | 19.30 MB | 1 年前3
 Pro Git 中文版 第2版 2.1.66e372b945b6e884e 1f7a7a472abf3dd9643fd615f6da379c4acb3e3a blob 10 19 7282 non delta: 15 objects chain length = 1: 3 objects .git/objects/pack/pack-978e03944f5c581011e6998cd0e9e30000905586.pack: ok 此处,033b40 码力 | 670 页 | 13.59 MB | 1 年前3 Pro Git 中文版 第2版 2.1.66e372b945b6e884e 1f7a7a472abf3dd9643fd615f6da379c4acb3e3a blob 10 19 7282 non delta: 15 objects chain length = 1: 3 objects .git/objects/pack/pack-978e03944f5c581011e6998cd0e9e30000905586.pack: ok 此处,033b40 码力 | 670 页 | 13.59 MB | 1 年前3
共 6 条
- 1














