From: Elijah Newren <newren@gmail.com>
To: "Mark T. Ortell" <mtortell@ra.rockwell.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: List of Known Issues for a particular release
Date: Thu, 11 Jul 2019 08:59:35 -0700 [thread overview]
Message-ID: <CABPp-BFr5TLNnjFxj_YRmt=z17U=ehxz1WjhqxDCA0aNf6v6JQ@mail.gmail.com> (raw)
In-Reply-To: <CY4PR2201MB1559C26C1D75B4F649AD38049AF30@CY4PR2201MB1559.namprd22.prod.outlook.com>
On Thu, Jul 11, 2019 at 8:50 AM Mark T. Ortell <mtortell@ra.rockwell.com> wrote:
>
> 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?
>
> Best Regards,
> Mark Ortell
Probably not in the format you want, and likely including noise that
isn't relevant, but in a clone of git.git you could run:
git grep ^test_expect_failure t/
next prev parent reply other threads:[~2019-07-11 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 15:28 List of Known Issues for a particular release Mark T. Ortell
2019-07-11 15:59 ` Elijah Newren [this message]
2019-07-11 19:02 ` EXTERNAL: " Mark T. Ortell
2019-07-11 20:04 ` Elijah Newren
2019-07-11 16:09 ` brian m. carlson
-- strict thread matches above, loose matches on Subject: below --
2019-07-12 20:44 Mark T. Ortell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABPp-BFr5TLNnjFxj_YRmt=z17U=ehxz1WjhqxDCA0aNf6v6JQ@mail.gmail.com' \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=mtortell@ra.rockwell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).