public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz93@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] special small-files USE flag without effect on dependencies: [ unicode ]
Date: Sat, 10 Feb 2024 19:58:44 -0500	[thread overview]
Message-ID: <8749fc12-e22c-49a8-bcc0-c4d8b72aeb9e@gmail.com> (raw)
In-Reply-To: <7b595327384c3d05246517251b237576@shitposting.expert>


[-- Attachment #1.1.1: Type: text/plain, Size: 1223 bytes --]

On 2/10/24 12:26 PM, stefan11111 wrote:
> On 2024-02-10 11:48, David Seifert wrote:
>>
>> Are users like you going to maintain and fix these obscure bugs too? I
>> don't recall seeing you sending in many fixes or patches, yet you seem
>> to be demanding that we go out of our way to accommodate you.
> 
> I've sent and made plenty of patches to support my use cases.
> I usually don't send patches to the ml and instead link them in bug
> reports, forum posts, etc.
> 
> Feel free to pull patches from my overlay or any other repo I have:
> https://github.com/stefan11111/stefan_overlay/


From every patch you've demonstrated in the past, my overall impression
is that you put zero effort into attempting to convince others, zero
effort into making the patches capable of supporting the toggleable use
case (no, commenting out lines wholesale is not a suitable patch, adding
a build option and an ifelse would be) and basically, in short...

... you've behaved in a way that guarantees that no patches of yours
will ever be merged upstream.

This is personally sad to me because I actually do think a number of
them would make good toggleable feature options for upstream.


-- 
Eli Schwartz

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-02-11  0:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 15:23 [gentoo-dev] special small-files USE flag without effect on dependencies: [ unicode ] Andrey Grozin
2024-02-09 15:43 ` Mike Gilbert
2024-02-09 15:54 ` Ionen Wolkens
2024-02-09 16:07   ` Michael Orlitzky
2024-02-09 16:57     ` Mike Gilbert
2024-02-09 17:17       ` Michael Orlitzky
2024-02-09 18:40         ` Mike Gilbert
2024-02-09 19:09         ` Eli Schwartz
2024-02-09 19:57           ` Michael Orlitzky
2024-02-09 21:04             ` Eli Schwartz
2024-02-09 21:25               ` Michael Orlitzky
2024-02-09 21:56                 ` Eli Schwartz
2024-02-09 22:56                   ` stefan11111
2024-02-10  0:03                     ` Matt Jolly
2024-02-10 11:48                     ` David Seifert
2024-02-10 17:26                       ` stefan11111
2024-02-11  0:58                         ` Eli Schwartz [this message]
2024-02-10 11:22                   ` orbea
2024-02-11  0:58                     ` Eli Schwartz
2024-02-10  0:04               ` Sam James
2024-02-11  0:42                 ` Eli Schwartz
2024-02-11  3:46                   ` Sam James
2024-02-11  3:56                     ` Eli Schwartz
2024-02-12  4:54                     ` Andrey Grozin
2024-02-10  0:00             ` Sam James
2024-02-09 23:52 ` Sam James

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=8749fc12-e22c-49a8-bcc0-c4d8b72aeb9e@gmail.com \
    --to=eschwartz93@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /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