Re: [RFC PATCH] docs: document upcoming breaking changes
- From
- Dragan Simic <dsimic@manjaro.org>
- Date
- May 10, 2024, 12:43 UTC
- Message-ID
- <bcaa054e4081a43bef349a1079895374@manjaro.org>
- In-Reply-To
- <Zj4Gx6LGSoTGc3eW@tanuki>
Hello Patrick,
On 2024-05-10 13:36, Patrick Steinhardt wrote:
Show 19 quoted lines
> On Wed, May 08, 2024 at 05:59:01PM +0200, Dragan Simic wrote: >> On 2024-05-08 15:54, Patrick Steinhardt wrote: >> > Okay, I see how that may make sense for some parts. I guess one of the >> > motivations here is things like git-checkout(1) and git-switch(1) / >> > git-restore(1)? >> >> As I wrote already, [1] I really see no reasons why git-switch(1) or >> git-restore(1) should be deprecated. That would make zero sense to >> me. >> >> [1] >> https://lore.kernel.org/git/3d84f2eac9b03eda814332d73b5d5ba6@manjaro.org/ > > Note that the discussion here is the other way round: whether we want > to > eventually deprecate tools like git-checkout(1) that have newer > replacements. Junio argues that there being a replacement is not by > itself a good enough reason to eventually remove the old one, which I'm > fine with.
I agree that not deprecating git-checkout(1) and similar utilities is the way to go. It's rather safe to assume that many users still use them, despite the existence of the newer replacements. Also, not just users, but various scripts.