All of lore.kernel.org
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Jorge Ramirez <jro@xenomai.org>
Cc: "Xenomai@xenomai.org" <Xenomai@xenomai.org>
Subject: Re: [Xenomai] [RFC] Service hosting for Xenomai
Date: Mon, 27 Nov 2017 10:57:26 -0500	[thread overview]
Message-ID: <20171127155726.l5rxwgilynue6gug@csclub.uwaterloo.ca> (raw)
In-Reply-To: <92228043-c203-d4c2-7088-6f16e66f7cb4@xenomai.org>

On Sun, Nov 26, 2017 at 06:49:12PM +0100, Jorge Ramirez wrote:
> we all like the kernel workflow and the release process. In fact, in seems
> to scale ad-infinitum.
> however we dont have this need AFAIK.
> 
> all the default configs in the tree. 10, 20, 200, whatever.
> 
> complex stuff gets discussed in ML.
> simple stuff, information sharing, light details, simple blocks, pings, that
> is what IRC is for.
> 
> tends to works well;
> maybe try joining #ffmpeg,#kodi, #u-boot, ##linux-msm, etc and have a peak
> if you are not used to IRC.

I used to spend a lot of time on IRC.  Way too much time helping people
with linux issues of various kinds.  Doing things live was way too time
consuming, so I decided to ban myself from IRC.  I think it has been
almost 10 years now that I have avoided IRC.

> this would be ridiculous if it was for an upstream complex review.
> 
> if it is for a quick discussion with someone in the channel, sure, you can
> send a patch - as a code snippet - using paste services [1] obviously.
> This is very common these days.

The nice thing with the mailing list ist that everyone that is interested
gets to see it.  With IRC only those that were around on IRC at the time
get to see it.

> what do you mean about random websites? you lost me there.

Some people think webforums are better for discussions than mailing lists.
But that is yet another place you have to think to go read.

-- 
Len Sorensen


  parent reply	other threads:[~2017-11-27 15:57 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 17:11 [Xenomai] [RFC] RTnet, Analogy and the elephant in the room Philippe Gerum
2017-11-21 17:26 ` Greg Gallagher
2017-11-22 15:24   ` Philippe Gerum
2017-11-21 19:27 ` Auel, Kendall
2017-11-22 15:32   ` Philippe Gerum
2017-11-22 20:27     ` Jan Kiszka
2017-11-23 11:42       ` [Xenomai] [RFC] Service hosting for Xenomai Philippe Gerum
2017-11-23 12:38         ` Jorge Ramirez
2017-11-23 20:35           ` Lennart Sorensen
2017-11-26 17:49             ` Jorge Ramirez
2017-11-27 15:56               ` Jorge Ramirez
2017-11-27 15:57               ` Lennart Sorensen [this message]
2017-11-27 20:47             ` Wolfgang Denk
2017-11-23 20:36           ` Philippe Gerum
2017-11-23 22:00             ` Jorge Ramirez
2017-11-23 12:52         ` Henning Schild
2017-11-23 13:18           ` Jorge Ramirez
2017-11-23 19:39             ` Jan Kiszka
2017-11-26 17:40               ` Jorge Ramirez
2017-11-27 20:41         ` Wolfgang Denk
2017-11-27 21:44           ` Philippe Gerum
2017-11-28  8:47             ` Henning Schild
2017-11-23 20:27       ` [Xenomai] [RFC] RTnet, Analogy and the elephant in the room Philippe Gerum
2017-11-21 19:54 ` Dmitriy Cherkasov
2017-11-22 16:23   ` Philippe Gerum
2017-11-22 12:33 ` Leopold Palomo-Avellaneda
2017-11-22 15:17   ` Greg Gallagher
2017-11-23 11:01   ` Philippe Gerum
2017-11-22 20:26 ` Jan Kiszka
2017-11-23 12:21   ` Henning Schild
2017-11-23 14:22     ` Giulio Moro
2017-11-23 20:45   ` Philippe Gerum
2017-11-24  8:52     ` Stéphane LOS
2017-11-24  9:00       ` Stéphane LOS
2017-11-24 10:46 ` Stéphane Ancelot
2017-11-25 20:32   ` Philippe Gerum
2017-12-01 15:09     ` Stéphane Ancelot
2017-12-01 15:12       ` Stéphane Ancelot
2017-11-26 18:00   ` Jorge Ramirez
2017-12-01  9:59 ` Stéphane Ancelot
2017-11-23 12:17 [Xenomai] [RFC] Service hosting for Xenomai Norbert Lange

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=20171127155726.l5rxwgilynue6gug@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=Xenomai@xenomai.org \
    --cc=jro@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.