From: Dirk Gouders <dirk@gouders.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Possible problem in --pretty=reference?
Date: Fri, 12 Dec 2025 14:28:08 +0100 [thread overview]
Message-ID: <ghbjk3bziv.fsf@gouders.net> (raw)
In-Reply-To: <ghfr9fbznh.fsf@gouders.net> (Dirk Gouders's message of "Fri, 12 Dec 2025 14:25:22 +0100")
Please ignore the previous mail, seems I am overworked.
Sorry for the noise.
Dirk
prev parent reply other threads:[~2025-12-12 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 13:25 Possible problem in --pretty=reference? Dirk Gouders
2025-12-12 13:28 ` Dirk Gouders [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ghbjk3bziv.fsf@gouders.net \
--to=dirk@gouders.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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 NNTP newsgroup(s).