From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] ##edbrowse on freenode
Date: Fri, 20 Jan 2017 14:15:39 -0500 [thread overview]
Message-ID: <20170020141539.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1701191337010.7648@carhart.net>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
> I just made an ##edbrowse on freenode and am sitting in there..
Ok I finally logged into this chat but nobody else is there.
If we run with this then I need to reallocate my consoles, as each irc channel consumes 2 consoles.
I already have 2 for the speakup chat, which I want to keep rolling, as it is often amusing over there.
Sometimes we're just talking about the weather, and sometimes we've had our edbrowse chats over there.
So I can maintain another, separate, dedicated chat for edbrowse, which I think would be used very infrequently, or I could suggest that Kevin just join the speakup channel, and listen to us talk about the weather, and once in a while we discuss edbrowse things there, as we have before.
I'm not saying which approach is better.
Karl Dahlke
next prev parent reply other threads:[~2017-01-20 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 21:38 Kevin Carhart
2017-01-20 19:15 ` Karl Dahlke [this message]
2017-01-21 5:49 ` Kevin Carhart
2017-01-21 5:56 ` Karl Dahlke
2017-01-21 11:29 ` Chuck Hallenbeck
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=20170020141539.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.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).