git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stephen Harding <stharding@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: I still use this!
Date: Tue, 30 Sep 2025 13:02:33 -0700	[thread overview]
Message-ID: <xmqqldlv4skm.fsf@gitster.g> (raw)
In-Reply-To: <CAKu9fqx-fkOmKLby0mWU8D-T9vL1oY49kVLN2zWwhyfTUKSPsw@mail.gmail.com> (Stephen Harding's message of "Tue, 30 Sep 2025 12:49:16 -0600")

Stephen Harding <stharding@gmail.com> writes:

> I just encountered this:
>
> 'git whatchanged' is nominated for removal.
> If you still use this command, please add an extra
> option, '--i-still-use-this', on the command line
> and let us know you still use it by sending an e-mail
> to <git@vger.kernel.org>.  Thanks.
> fatal: refusing to run without --i-still-use-this
>
>
> I use oh-my-zsh and I rely on the git aliases. I used this today:
>
> which gwch
> gwch: aliased to git whatchanged -p --abbrev-commit --pretty=medium
>
> and apparently you want me to send you an email to prove that I, an
> actual human really do use that ...

It is not about proving, and sending an email will not change our
plan, but it gives users an opportunity to tell us a use case where
no possible workaround exists, which we haven't anticipated.

You can change your alias to

    git log --no-merges -p --abbrev-commit --pretty=medium

and should get output identical to what you are getting.  Also, I
think "--pretty=medium" is the default.




  parent reply	other threads:[~2025-09-30 20:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 18:49 I still use this! Stephen Harding
2025-09-30 19:57 ` Kristoffer Haugsbakk
2025-09-30 20:02 ` Junio C Hamano [this message]
2025-10-03 16:38   ` Stephen Harding
  -- strict thread matches above, loose matches on Subject: below --
2025-08-31 22:21 wafkse
2025-09-01  6:58 ` Kristoffer Haugsbakk

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=xmqqldlv4skm.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=stharding@gmail.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).