From: Sergey Organov <sorganov@gmail•com>
To: Glen Choo <chooglen@google•com>
Cc: Junio C Hamano <gitster@pobox•com>, git@vger•kernel.org
Subject: Re: What's cooking in git.git (Feb 2023, #01; Thu, 2)
Date: Thu, 02 Mar 2023 17:38:07 +0300 [thread overview]
Message-ID: <875ybjrzg0.fsf@osv.gnss.ru> (raw)
In-Reply-To: <kl6lk0003u41.fsf@chooglen-macbookpro.roam.corp.google.com> (Glen Choo's message of "Wed, 01 Mar 2023 15:54:54 -0800")
Glen Choo <chooglen@google•com> writes:
> Hi Sergey!
>
> Sergey Organov <sorganov@gmail•com> writes:
>
>>>> This is still marked as "probably won't merge" in the recent "what's
>>>> cooking". Could it be merged, please?
>>>
>>> I found the explanation given by Glen last time you mentioned the
>>> topic much better written than anything I would write myself, and I
>>> haven't seen any new input in the message I am responding to, so...
>>>
>>> https://lore.kernel.org/git/kl6lr0v2i0gn.fsf@chooglen-macbookpro.roam.corp.google.com/
>>
>> I believe I've addressed it with this:
>>
>> https://lore.kernel.org/git/87wn4tej2f.fsf@osv.gnss.ru/
>>
>> and seen no follow-up since then.
>
> Sorry for the lack of response, especially if it seemed like your
> concerns were not listened to. I did try crafting a response when it was
> first written, but it didn't end up adding anything new and valuable to
> the conversation, so I dropped it.
>
> I'll leave an updated response, but unfortunately, I am still of the
> opinion that we shouldn't merge this series.
The primary question here is: why don't allow me to get the behavior I
need, provided it has no impact on anybody else, unless they decide they
need it too? I've already performed "you need it, -- do it yourself"
dance, along with documentation and tests, so may I be rewarded by
getting this feature finally in, please?
Thanks,
-- Sergey Organov
next prev parent reply other threads:[~2023-03-02 14:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 4:02 What's cooking in git.git (Feb 2023, #01; Thu, 2) Junio C Hamano
2023-02-04 9:33 ` Sergey Organov
2023-02-06 18:35 ` Junio C Hamano
2023-02-06 21:35 ` Sergey Organov
2023-03-01 18:40 ` Sergey Organov
2023-03-01 22:15 ` Junio C Hamano
2023-03-01 22:26 ` Sergey Organov
2023-03-01 23:54 ` Glen Choo
2023-03-02 14:38 ` Sergey Organov [this message]
2023-02-07 4:06 ` so/diff-merges-more (was Re: What's cooking in git.git (Feb 2023, #01; Thu, 2)) Glen Choo
2023-02-07 12:50 ` Sergey Organov
2023-03-02 0:37 ` Glen Choo
2023-03-02 16:15 ` Junio C Hamano
2023-03-02 16:57 ` Sergey Organov
2023-03-06 22:22 ` Glen Choo
2023-03-07 10:02 ` Sergey Organov
2023-03-07 17:54 ` Junio C Hamano
2023-03-08 22:19 ` Sergey Organov
2023-03-08 23:08 ` Junio C Hamano
2023-03-09 13:54 ` Sergey Organov
2023-03-09 17:43 ` Glen Choo
2023-03-09 19:56 ` Sergey Organov
2023-03-10 21:19 ` Glen Choo
2023-03-10 21:47 ` Junio C Hamano
2023-03-17 14:18 ` Sergey Organov
2023-03-18 0:08 ` Junio C Hamano
2023-03-25 16:55 ` Sergey Organov
2023-03-29 7:43 ` Sergey Organov
2023-03-29 8:06 ` Sergey Organov
2023-02-08 17:22 ` ds/bundle-uri-5 (was: " Victoria Dye
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=875ybjrzg0.fsf@osv.gnss.ru \
--to=sorganov@gmail$(echo .)com \
--cc=chooglen@google$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/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