public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "S0AndS0 of Digital Mercenaries LLC"
	<S0AndS0@digital-mercenaries•com>,
	git@vger•kernel.org
Subject: Re: I still use this/these
Date: Tue, 23 Sep 2025 00:18:59 +0200	[thread overview]
Message-ID: <fd993486-069b-445a-ae91-a0f149fd3ea8@app.fastmail.com> (raw)
In-Reply-To: <8f201082-07b5-44a1-88cf-d6db551a598c@digital-mercenaries.com>

On Tue, Sep 23, 2025, at 00:11, S0AndS0 of Digital Mercenaries LLC wrote:
> Recently, as of `git version 2.51.0`, running the following commands be
> popping
> warnings;
>
>      git whatchanged <path>
>
>      git log --since="$(date --date='-2 weeks' +%F)"
>
> ...  Warnings stating those using certain features slated for removal should
> email y'all about `--i-still-use-this`. If there are alternatives I can
> alias,
> that will remain functional, please do let those like me know. Maybe via the
> same sorta warning system.

You can use

    git log --raw --no-merges

If you want the same behavior.

You can also replace `--raw` with `--stat` or `--name-only` if you want
the list of files without the filemode, hashes, and change type (like
M).

  reply	other threads:[~2025-09-22 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 22:11 I still use this/these S0AndS0 of Digital Mercenaries LLC
2025-09-22 22:18 ` Kristoffer Haugsbakk [this message]
2025-09-23  0:55   ` S0AndS0 of Digital Mercenaries LLC
2025-09-23 13:04     ` D. Ben Knoble
2025-09-23 16:36       ` S0AndS0 of Digital Mercenaries LLC

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=fd993486-069b-445a-ae91-a0f149fd3ea8@app.fastmail.com \
    --to=kristofferhaugsbakk@fastmail$(echo .)com \
    --cc=S0AndS0@digital-mercenaries$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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