Re: [PATCH 0/5] Advice on checkout dirty files

From: Arsh Srivastava <arshsrivastava00@gmail.com>
Date: Mar 10, 2026, 16:08 UTC
Message-ID: <CAOAgETMw2LdTpW3XjE3nDF61T9Fixa0r0tT+fWpc6DEXsREAmQ@mail.gmail.com>
In-Reply-To: <xmqqv7f3wv51.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

> It is understood as author that I understand.
> It is the users who need to understand.
> Potential risks for the user.

As informed by Karthik Nayak <karthik.188@gmail.com> and Patrick Steinhardt <ps@pks.im>. My PR seemed to have redundancy for which I will create a v4 for my PR removing it and giving it proper description for users to understand the possible risks of using -m.

Signed-off-by: Arsh Srivastava <arshsrivastava00@gmail.com>

On Tue, 10 Mar 2026 at 21:10, Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

>
> Arsh Srivastava <arshsrivastava00@gmail.com> writes:
>
> > As per the recommendation of Phillip Wood <phillip.wood123@gmail.com>
> > I have changed my files and added git checkout -m after understanding
> > its significance :)
>
> It is a given that you as the author of the patch understand it.
> What I meant was that the users who get the recommendation need to
> be told about the potential issues.