From: Junio C Hamano <gitster@pobox.com>
To: Thomas Braun <thomas.braun@virtuell-zuhause.de>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [ANNOUNCE] Git v2.38.0
Date: Wed, 05 Oct 2022 12:22:20 -0700 [thread overview]
Message-ID: <xmqqlepuoz2r.fsf@gitster.g> (raw)
In-Reply-To: <c8d43514-6f78-387c-b5aa-0657c75d5b4e@virtuell-zuhause.de> (Thomas Braun's message of "Wed, 5 Oct 2022 11:39:11 +0200")
Thomas Braun <thomas.braun@virtuell-zuhause.de> writes:
> On 03.10.2022 19:26, Junio C Hamano wrote:
>
> Hi Junio and Ævar,
>
> the last git release has
>
>> submodule--helper: remove unused "list" helper
>
> in the shortlog which is 31955475 (submodule--helper: remove unused
> "list" helper, 2022-09-01).
X-<.
> Now the inevitable "I'm using this in production since 5 years and now
> it's broken" has happened.
X-< again. Next time when you are using unsupported implementation
detail, please report when the potential breakage is still in 'next'
and not down in 'master'.
> Just for the record "git submodule status" is a good replacement for
> my case. I happen to need it on Windows using a CMD shell.
>
> Is there a general rule that commands which have "--helper" in them
> should not be relied on?
A good rule of thumb is to consider anything with double-dash as an
implementation detail that are not end-user facing, I would say.
Thanks, and sorry for the breakage.
prev parent reply other threads:[~2022-10-05 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 17:26 [ANNOUNCE] Git v2.38.0 Junio C Hamano
2022-10-05 9:39 ` Thomas Braun
2022-10-05 19:22 ` Junio C Hamano [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=xmqqlepuoz2r.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=thomas.braun@virtuell-zuhause.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.