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

Re: git/git-scm.com GH Issue Tracker

From
Samuel Lijin <sxlijin@gmail.com>
Date
Feb 8, 2017, 00:33 UTC
Message-ID
<CAJZjrdU-UsWpNvjQ=eZi1wMUSWxRXLr5YNsgAce=z7Zt3yCTSA@mail.gmail.com>
In-Reply-To
<20170206183429.sd7255b3ovvg746c@sigill.intra.peff.net>
Finished going through and nailed the rest of the open issues!
# Irrelevant but it seems like someone should take a look
511 466
# Irrelevant to git-scm.com and should be closed
599 596 570 565 563 558 538 537 520 511 509 507 501 494 465
# Resolved, duplicate, or non-issue

596 593 592 588 587 585 583 576 575 573 572 547 546 543 540 539 529 521 516 515 504 503 502 496 491 490 476 473 470 467 463 460 456 454 451 413 377 265 257 95

# Relevant and should be kept open

597 595 591 586 578 544 532 518 513 512 500 493 466 448 416 410 381 379 140 13 12 11

That's all of them!
- Sam
On Mon, Feb 6, 2017 at 12:34 PM, Jeff King <peff@peff.net> wrote:
Show 12 quoted lines
> On Mon, Feb 06, 2017 at 12:15:08AM -0600, Samuel Lijin wrote:
>
>> I've went through a bunch of open issues on the git/git-scm.com repo
>> (specifically, everything after #600) and I think the bulk of them can
>> be closed.
>>
>> I've taken the liberty of classifying them as shown below.
>
> Thanks, this is incredibly helpful. I'll close the appropriate ones you
> identified.
>
> -Peff
Previous: Jeff King
Message 8 of 8 in “git/git-scm.com GH Issue Tracker”
  1. Samuel LijinFeb 6, 2017
  2. Thomas Ferris NicolaisenFeb 6, 2017
  3. Duy NguyenFeb 6, 2017
  4. Jeff KingFeb 6, 2017
  5. Junio C HamanoFeb 6, 2017
  6. Jeff KingFeb 6, 2017
  7. Jeff KingFeb 6, 2017
  8. Samuel LijinFeb 8, 2017

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.