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

Re: Git bug.

From
Kristoffer Haugsbakk <code@khaugsbakk.name>
Date
Apr 14, 2023, 09:26 UTC
Message-ID
<fe75dd24-344b-4c9b-b08f-af12f3beff11@app.fastmail.com>
In-Reply-To
<CAJN3DWqbR-9sNGT=Njei5PNSGKVKSOgrY4K=FXVjUKEFQ27bWg@mail.gmail.com>
On Fri, Apr 14, 2023, at 10:29, Gabriel Furstenheim Milerud wrote:
> Hi,
> Sorry if this is not the right address to report bugs. I'm following
> https://stackoverflow.com/questions/10728104/where-can-i-report-a-git-bug/10733251#10733251
LGTM.

VonC has amazing Git answers on SO, but I feel that this changelog-type answer is *too much* for a procedure which is just (based on the bug reports from the last month or so):

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
So basically the sibling answer https://stackoverflow.com/a/70175922/1725151
-- 
Kristoffer Haugsbakk
Previous: Gabriel Furstenheim Milerud
Message 2 of 2 in “Git bug.”
  1. Gabriel Furstenheim MilerudApr 14, 2023
  2. Kristoffer HaugsbakkApr 14, 2023

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.