From: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
To: "Gabriel Furstenheim Milerud" <furstenheim@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git bug.
Date: Fri, 14 Apr 2023 11:26:30 +0200 [thread overview]
Message-ID: <fe75dd24-344b-4c9b-b08f-af12f3beff11@app.fastmail.com> (raw)
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
next prev parent reply other threads:[~2023-04-14 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 8:29 Git bug Gabriel Furstenheim Milerud
2023-04-14 9:26 ` Kristoffer Haugsbakk [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-08 19:32 git bug Justin Tang
2024-02-04 23:42 moti sd
2024-02-05 6:47 ` Patrick Steinhardt
2023-04-14 9:41 Git bug Gabriel Furstenheim Milerud
2023-04-14 16:07 ` René Scharfe
[not found] ` <CAJN3DWpvh8uHnRFnaPgg8U6dW=3xP9YULBe-xfeTAg2SV7K+oQ@mail.gmail.com>
2023-04-17 9:46 ` Gabriel Furstenheim Milerud
2020-08-06 14:59 git bug PANEL Christian
2020-08-06 14:48 PANEL Christian
2020-08-06 20:23 ` René Scharfe
2020-08-07 0:02 ` Jeff King
2020-08-10 5:56 ` René Scharfe
2020-08-10 17:20 ` PANEL Christian
2012-10-22 16:28 git BUG Коньков Евгений
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=fe75dd24-344b-4c9b-b08f-af12f3beff11@app.fastmail.com \
--to=code@khaugsbakk.name \
--cc=furstenheim@gmail.com \
--cc=git@vger.kernel.org \
/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).