Git development
 help / color / mirror / Atom feed
From: Sven Weiland <sven.weiland@tngtech.com>
To: git@vger.kernel.org
Subject: git reflog expire output inconsistency
Date: Wed, 6 May 2026 14:26:56 +0200	[thread overview]
Message-ID: <b46cbce8-d2bb-46d2-bdd3-545422813d6b@tngtech.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1397 bytes --]

Hi,

I noticed a small inconsistency in the output of the git reflog expire 
command.


Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)

	1. Fill reflog HEAD with something
	2. git reflog expire --verbose --expire=now --dry-run HEAD

What did you expect to happen? (Expected behavior)

	would prune checkout: <something>

What happened instead? (Actual behavior)

	prune checkout: <something>

What's different between what you expected and what actually happened?

	It omitted "would ".

Anything else you want to add:

	It's just a logging thing the behavior is as expected from the dry-run.

Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.54.0
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
rust: disabled
gettext: enabled
libcurl: 8.5.0
zlib: 1.3
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1
uname: Linux 6.17.0-1017-oem #17-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 27 
13:48:03 UTC 2026 x86_64
compiler info: gnuc: 13.3
libc info: glibc: 2.39
$SHELL (typically, interactive shell): /usr/bin/zsh


[Enabled Hooks]


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

                 reply	other threads:[~2026-05-06 12:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=b46cbce8-d2bb-46d2-bdd3-545422813d6b@tngtech.com \
    --to=sven.weiland@tngtech.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox