Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Patrick Ouellette <pouelle@debian.org>
Cc: node@packages.debian.org, nodejs@packages.debian.org,
	linux-hams@vger.kernel.org
Subject: Re: Node.js and it's future in debian
Date: Wed, 2 May 2012 15:31:40 -0500	[thread overview]
Message-ID: <20120502203140.GA31840@burratino> (raw)
In-Reply-To: <20120502200426.GF7390@flying-gecko.net>

Patrick Ouellette wrote:

>                                   (The "patch" sent does not address
> automatically updating anything)

This is very funny.  You are putting patch in quotes, but it[1] was a
real patch.  It did not automatically update anything because it was
meant to be a simple patch to get work started.  I volunteered to
write further patches once I got feedback on that one, and then I got
no direct feedback on it, just occasional passive-aggressive comments
like the above.

[...]
>> Because you did not ask for one.  Instead you have been wasting time
>> arguing and defending against an opponent you seem to assume is not
>> going to care or listen to you.
>
> The Node.js people apparently didn't ask for one either
> pot - kettle - black

The pot is presumably me.  But I am not a Node.js person.  The Debian
Node.js package maintainers have been friendly and helpful when I
contacted them, and they seem to be willing to help work on including
a nodejs command upstream and modifying Debian packages to use it.
They also seemed willing to remove the node command from nodejs if a
consensus in the project were to develop that that was needed.

Just for completeness, I should mention that Jaime Robles on the
ham radio package maintenance side has been friendly, too.

You have made it clear that you are more interested in punishing
people than in making wheezy better, so I don't think we have anything
left to talk about.  I'll contact the technical committee and leave
this in their capable hands.

Thanks for some useful clarifications,
Jonathan

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=20;bug=614907

  reply	other threads:[~2012-05-02 20:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACxjfDH5zYth6Q-ZDLDafqNEczbF3BqaGRcAhsaiPEnApbiUuA@mail.gmail.com>
     [not found] ` <20120501205524.GI30521@flying-gecko.net>
     [not found]   ` <20120501215305.GA1250@burratino>
     [not found]     ` <20120501221659.GA11430@flying-gecko.net>
     [not found]       ` <20120502065003.GB2410@burratino>
     [not found]         ` <20120502165031.GC7390@flying-gecko.net>
     [not found]           ` <20120502171349.GA23806@burratino>
2012-05-02 20:04             ` Node.js and it's future in debian Patrick Ouellette
2012-05-02 20:31               ` Jonathan Nieder [this message]
2012-05-03 15:29               ` David Ranch
2012-05-03 15:33               ` David Ranch
2012-05-03 16:17                 ` Marius Petrescu
2012-05-03 17:08                   ` Patrick Ouellette
2012-05-03 17:05                 ` Patrick Ouellette
2012-05-03 18:51                   ` Jonathan Nieder
2012-05-03 19:48                     ` Gordon JC Pearc e
2012-05-03 23:10                     ` Hans-Peter F. Oeste
2012-05-04  4:09                     ` David Ranch
2012-05-04  4:28                       ` Ray Wells
2012-05-04  4:46                       ` Jonathan Nieder
2012-05-04 12:31                   ` DL1SIG
2012-05-04 13:29                     ` [Pkg-javascript-devel] " Emilien Klein
2012-05-04 14:31                     ` Patrick Ouellette
2012-05-04  7:38               ` walter harms

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=20120502203140.GA31840@burratino \
    --to=jrnieder@gmail.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=node@packages.debian.org \
    --cc=nodejs@packages.debian.org \
    --cc=pouelle@debian.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