netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "chaosesqueteam@yahoo.com" <chaosesqueteam@yahoo.com>,
	Linux Networking <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Julia Lawall <julia.lawall@inria.fr>
Subject: Re: I can't get contributors for my C project. Can you help?
Date: Sun, 8 Oct 2023 06:59:49 +0700	[thread overview]
Message-ID: <ZSHw9aGGHOpJ825J@debian.me> (raw)
In-Reply-To: <457035954.3503192.1696688953071@mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]

[trim Cc: list as it becomes mess]

On Sat, Oct 07, 2023 at 02:29:13PM +0000, chaosesqueteam@yahoo.com wrote:
> Bagas; 
> There is no other place that C projects are talked about. In the past I could get help and contributors just asking; now you are all silo'd in your own little worlds and seethe with extreme anger or some castrated-drug-stupor in "irony" and smugness against anyone that asks for some contributors. Every single place bans anyone that asks for contributors to free-software projects.
> 
> You feel you are superior because you "did code" 10 years ago and "support trans rights".
> When asked to even allow a message to be seen that asks for contributors, in this case a file format, to a fellow C project: you seethe or pretend you are superior.
> As if I didn't know where I was sending the message? 
> I sent it to: RMS, ESR, Bruce Perens, redhat, OpenBSD, NetBSD, and Line-Unix. All C projects. Just like this engine.
> I'm just asking for contributors. Not promoting "outrecehery" (some feminist BS), Not "master vs main", not "noo can't call things whitelist/blacklist", and not Codes Of Conducts for free contributors. I'm just asking for C programming help for 3d file formats I'd like to add to this free-software project.
> 
> sourceforge.net/p/chaosesqueanthology/tickets/2/ 
> 

Please don't top-post; reply inline with appropriate context instead.

I repeat, this is not userspace application support forum. This (LKML)
is for Linux kernel development instead. You better get support somewhere
else.

Bye!

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-10-07 23:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <875007189.3298572.1696619900247.ref@mail.yahoo.com>
2023-10-06 19:18 ` I can't get contributors for my C project. Can you help? chaosesqueteam
2023-10-07  8:56   ` Bagas Sanjaya
2023-10-07 14:11     ` chaosesqueteam
2023-10-07 14:29     ` chaosesqueteam
2023-10-07 23:59       ` Bagas Sanjaya [this message]
     [not found]       ` <CAK2MWOsK=pTKADr1kUuj=fvmRB=X2Z0+SkWQ9PTSxCqOVCq39A@mail.gmail.com>
2023-10-09  7:15         ` Bagas Sanjaya
2023-10-10 15:01         ` chaosesqueteam
     [not found]           ` <CAK2MWOurH4AHGd3ntgVvg-+Z6rNZriO2xQm9_RNqpUMwWWQCkg@mail.gmail.com>
     [not found]             ` <1891850654.636910.1701859570489@mail.yahoo.com>
2023-12-16 14:18               ` chaosesqueteam
     [not found]                 ` <ZX3TEj9LyyHg1cHQ@skapet.bsdly.net>
2023-12-16 17:56                   ` chaosesqueteam
     [not found] <bf818dab301fb4e4@pg4>
     [not found] ` <1299484129.1816565.1702749635639@mail.yahoo.com>
     [not found]   ` <ZX34jd2Qhx2rObC_@www.stare.cz>
2023-12-24 14:12     ` chaosesqueteam
     [not found]   ` <20231216183721.22838388@Polaris>
2023-12-24 19:21     ` chaosesqueteam
     [not found] <549578214.4148875.1703446908152.ref@mail.yahoo.com>
2023-12-24 19:41 ` chaosesqueteam
2023-12-24 20:25   ` Rudy Zijlstra
2023-12-25 10:24     ` chaosesqueteam

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=ZSHw9aGGHOpJ825J@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=chaosesqueteam@yahoo.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=julia.lawall@inria.fr \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).