9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] Vanilla Plan 9 or one of the flavors?
Date: Mon,  6 Jan 2014 10:35:35 -0500	[thread overview]
Message-ID: <d36bb69e0074caf3d15ecc2965df67c4@9srv.net> (raw)
In-Reply-To: <C82D4878-B873-421D-95C1-4EB77921765A@orthanc.ca>

// In the case of 'The Labs' these days, sharing seems to be
// an anathema.  Acceptance of outside code?  Never.

Look, we've got enough problems without you making things
up which are trivially false:

	: root; pwd
	/n/sources/patch/applied
	: root; for (i in `{ls -rt | tail}) {echo -n $i':	' ; sed 's/@.+//' < $i/email}
	ndb-authdom-hamnavoe:	miller
	bcm-firmware-date:	miller
	5c-nan-cmp:	miller
	5l-incfloat:	miller
	acme-disk-read:	nemo
	fdisk-64-bit-table:	quanstro
	southbridge-8086-1c44:	davide+p9
	ether8169-macv34:	davide+p9
	file-aac-audio:	steve
	ape-cc-objtype:	lunaria21

That is not what "Never" looks like. This is not to say that there
are no issues with patch evaluation or sources' management;
there are. But creating a caricature of the issue is remarkably
unhelpful, at best.

// For the rest of us, share my code by accepting what I wrote -
// verbatim - or just peer at my work on the pedestal I
// constructed over here?  Feh.

Also, obviously false. Both mainline and 9atom have a patch
repository (and Erik's done a particularly good job making it extra
useful by using that for his own 9atom changes), and the 9front
guys have everything in a hg repo on Google Code (say what you
will about hg and/or Google Code, but it pretty much eliminates
the sorts of complaints you're making here). Lots of people make
patches available in contrib. What "pedestal" are you talking
about? Who's fought their code being reused elsewhere?

// What the fuck ever happened to 'community' ...

Ours has always been small, and never helped by people going
out of their way to trash the efforts of others, nor by inventing
issues to complain about.

Anthony




  parent reply	other threads:[~2014-01-06 15:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-31  2:02 Alex Jordan
2013-12-31  2:07 ` Alex Jordan
2013-12-31  4:33 ` erik quanstrom
2014-01-05 23:54   ` Alex Jordan
2014-01-06  0:03     ` Patryk Laurent
2014-01-06  4:03       ` Steven Stallion
2014-01-06  4:36         ` Lyndon Nerenberg
2014-01-06  4:41           ` Steven Stallion
2014-01-06  4:53             ` Lyndon Nerenberg
2014-01-06  5:01               ` Steven Stallion
2014-01-06  5:09                 ` Lyndon Nerenberg
2014-01-06  5:13                   ` andrey mirtchovski
2014-01-06  5:16                     ` Steven Stallion
2014-01-06  5:28                   ` Patryk Laurent
2014-01-06  5:12                 ` Bruce Ellis
2014-01-06 15:35               ` a [this message]
2014-01-06 16:40                 ` Aram Hăvărneanu
2014-01-06 16:54                   ` Anthony Sorace
2014-01-06 17:21                     ` lucio
2014-01-06 17:09                   ` tlaronde
2014-01-06 17:25                     ` lucio
2014-01-06 20:13                   ` Kurt H Maier
2014-01-06  4:42           ` balaji
2014-01-06 20:05           ` Kurt H Maier
2014-01-06  7:08         ` Alex Jordan
2014-01-06  7:39           ` cinap_lenrek
2014-01-06  7:49             ` Alex Jordan
2014-01-06 10:48               ` Paul Clark
2014-01-06 17:29               ` Dave Eckhardt
2014-01-06 12:20             ` Richard Miller
2014-01-06 13:29           ` erik quanstrom
2014-01-07  6:58             ` Alex Jordan
2014-01-07  8:32               ` Andrés Domínguez
2014-01-07 14:00               ` erik quanstrom

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=d36bb69e0074caf3d15ecc2965df67c4@9srv.net \
    --to=a@9srv.net \
    --cc=9fans@9fans.net \
    /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).