git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: List of Known Issues for a particular release

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jul 11, 2019, 16:09 UTC
Message-ID
<20190711160948.GK9224@genre.crustytoothpaste.net>
In-Reply-To
<CY4PR2201MB1559C26C1D75B4F649AD38049AF30@CY4PR2201MB1559.namprd22.prod.outlook.com>
On 2019-07-11 at 15:28:27, Mark T. Ortell wrote:
Show 5 quoted lines
> Hello,
> 
> I am doing a software tool assessment for functional safety and I am reviewing the use of Git as the SCM. One thing that I need to do is review the list of "known issues" with the Git release being used. I have gone through the release notes and found that it only contains the fixes and enhancements in a particular release of Git, it does not contain a list of known issues/errata in a particular release. The github project also does not include the bug tracking list, so I am not able to figure out a way to review the known issues for a particular release. I considered reviewing the fixes in releases beyond the release used, but that has 2 problems. One, it doesn't contain any issues that are yet to be fixed. Two, only the fixes in the "next" release are truly relevant because fixes after that could have been introduced in a release after the release being used. An additional note is that the Git for Windows project does provide a list of known issues in the install
> 
> Could someone in this mailing list assist me in finding the known issues for a particular version?

It sounds like what you're asking is for a bug tracker that lists all known issues. Git doesn't have one of those; we instead use the mailing list for reporting issues. We've considered using a bug tracker in the past, but the idea hasn't caught on yet.

The GitHub project is a mirror; it isn't the canonical resource, and the Git project doesn't use it for issues or pull requests. Both of these are also the same policy as for the Linux kernel[0], which you may or may not use.

If you're looking for an easy way to check off a compliance box, you may need to work with your management and/or auditors to see what approach you use for other software (such as Linux) that has nontraditional bug reporting practices. If you typically use a Linux distro that addresses this issue for you, then you'll probably want to use Git from that source as well.

Alternatively, you can use Git for Windows on a non-Windows system; it should compile and run just fine on Linux, macOS, and Windows, although it tends to carry more patches than Git itself.

[0] Yes, kernel.org has a bug tracker, but it is known to be incomplete and many issues are raised only on the various mailing lists.

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
Previous: Elijah Newren
Message 5 of 5 in “List of Known Issues for a particular release”
  1. Mark T. OrtellJul 11, 2019
  2. Elijah NewrenJul 11, 2019
  3. Mark T. OrtellJul 11, 2019
  4. Elijah NewrenJul 11, 2019
  5. brian m. carlsonJul 11, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.