TLDR; 以 < a href=" https://public-inbox.org/git/fe75d24-344b-4c9b-b08f-af12f3beff11@app.fastmail.com/T/#u" rel="nofollow noreferrer" 命名, 在 Git 邮件地址列表 中提及 :

1. Run git bugreport
2. Edit the file by filling out the blanks and removing irrelevant stuff (follow the instructions)
3. Post the report as an inline plaintext email to [email protected] (again: plaintext, not HTML)

如“http://code.google.com/p/git-core/” Rel=“不跟随 nofolrer” >code google git-core _/a> (由>>>Charles Bailey ,其中指出>>>。

使用电子邮件地址,可向邮件地址列表发送对 Git 社群的问题或评论。错误报告应发送到此邮件列表 。

("https://lore.kernel.org/git/"rel="不跟随 noreferrer"> 邮件列表归档 )

更新 Q2 2020 时, 您现在有一个实际的 < enger * code> git bugreport < /code* /strong > 命令( 见下文结尾)

2015年更新:最新参考资料仍然是Git 社区页面 ,作为。

社群页面也指出“' http://www.chiark.greenend.org.uk/%7Esgtatham/bugs.html' rel=“不跟随无查询者''' 如何有效报告错误 ......”

如果您想要 < 坚固 > 贡献一个补丁 < / 坚固 >, 现在就转到 < a href=" https:// github.com/rtyley/submitgit" rel= “ 不随从 noreferr" \\\ penge{code>rtyley/submitgit

If you create a pull request on github.com/git/git/, submitGit can send it to the mailing list for you, correctly formatting the patches.
The discussion stays where it is—on the list—but at least that initial step is a little easier.

Update 2015: Git For Windows now lives on GitHub (github.com/git-for-windows), and produces very recent releases: 2.4.2+.
Msysgit is phased out, using msys2 64-bits, and resulting in git-for-windows.github.io instead of the old and now obsolete msysgit.github.io.

GitHub 镜像 repo 图像 < a href="https://gitub.com/git/git/git" rel= "nofollow noreferrer" > >git/git 存在,但不幸的是,没有用于问题或拉动请求。

更新 2019 : submitGit 还有一个替代方案:GitGadget

See commit c3a7dd7 (12 Mar 2019) by Jeff King (peff).
^{(Merged by Junio C Hamano -- gitster -- in commit 2d33728, 09 Apr 2019)}

point pull requesters to GitGitGadget

In the contributing guide and PR template seen by people who open pull requests on GitHub, we mention the submitGit tool, which gives an alternative to figuring out the mailing list.
These days we also have the similar GitGitGadget tool, and we should make it clear that this is also an option.

We could continue to mention both tools, but it s probably better to pick one in order to avoid overwhelming the user with choice.
After all, one of the purposes here is to reduce friction for first-time or infrequent contributors.

更喜欢GGG 有几个理由:

1. submitGit seems to still have a few rough edges. E.g., it doesn t munge timestamps to help threaded mail readers handled out-of-order delivery.
2. Subjectively, GGG seems to be more commonly used on the list these days, especially by list regulars.
3. GGG seems to be under more active development (likely related to point 2).

So let s actually swap out submitGit for GGG.
While we re there, let s put another link to the GGG page in the PR template, because that s where users who are learning about it for the first time will want to go. to read more.

在Git 2.25 (Q1 2020)中,有一个关于对象查点的辅导,为如何贡献/测试/报告错误提供了一个良好范例。

See commit e0479fa (11 Oct 2019) by Emily Shaffer (nasamuffin).
^{(Merged by Junio C Hamano -- gitster -- in commit 15d9f3d, 10 Nov 2019)}

documentation: add tutorial for object walking

签名:Emily Shaffer < /sup >
^{Helped-by: Eric Sunshine}

Existing documentation on object walks seems to be primarily intended as a reference for those already familiar with the procedure.
This tutorial attempts to give an entry-level guide to a couple of bare-bones object walks so that new Git contributors can learn the concepts without having to wade through options parsing or special casing.

The target audience is a Git contributor who is just getting started with the concept of object walking.
The goal is to prepare this contributor to be able to understand and modify existing commands which perform revision walks more easily, although it will also prepare contributors to create new commands which perform walks.

The tutorial covers a basic overview of the structs involved during object walk, setting up a basic commit walk, setting up a basic all-object walk, and adding some configuration changes to both walk types.
It intentionally does not cover how to create new commands or search for options from the command line or gitconfigs.

在rel=“不跟随 Noreferrerr>>https://github.com/nasamuffin/git/tree/revwalk 上有一个相关的补丁,该补丁载有本教程产生的代码的参考执行。

注:Git 2.27 (Q2 2020)对辅导进行了修改:

See commit e3f53ce (28 Mar 2020) by Johannes Schindelin (dscho).
^{(Merged by Junio C Hamano -- gitster -- in commit 7780604, 22 Apr 2020)}

MyFirstObjectWalk: remove unnecessary conditional statement

^{Signed-off-by: Johannes Schindelin}
经审查:Emily Shaffer

在给定例子中, commit 不能是 NULLL (因为这是循环条件:如果是 NULLL ,则循环体不会被输入)。 开发者花了一两秒钟才看到它因此是死代码。

避免让未来读者感到困惑。

Git 2.25 (Q1 2020),“强”GitGatget

See commit 3c8d754, commit 3ada78d, commit 4ed5562 (31 Oct 2019) by Emily Shaffer (nasamuffin).
^{(Merged by Junio C Hamano -- gitster -- in commit f089ddd, 01 Dec 2019)}

myfirstcontrib: hint to find gitgitgadget allower

签名:Emily Shaffer < /sup >