From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] alt and chanfree
Date: Tue, 14 Sep 2010 09:01:57 -0400 [thread overview]
Message-ID: <1c691961f042c7f6194f62781d377b4e@coraid.com> (raw)
In-Reply-To: <ae50545f10f809a845590d4a3d2c81ea@iram.fr>
On Tue Sep 14 06:11:35 EDT 2010, mathieu.lonjaret@gmail.com wrote:
> That's exactly the sense of my question, thanks.
> I didn't see in the man page if I should do that sort of cleaning up or
> not, it just says that the channel can be freed from either side. so I
> wasn't sure in what state alt() is expecting the Alt entries to be at
> all time.
isn't that what chanclose()/chanclosing() is for?
- erik
next prev parent reply other threads:[~2010-09-14 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 8:57 Mathieu Lonjaret
2010-09-14 9:55 ` roger peppe
2010-09-14 10:04 ` Mathieu Lonjaret
2010-09-14 13:01 ` erik quanstrom [this message]
2010-09-14 13:27 ` Mathieu Lonjaret
2010-09-14 13:30 ` erik quanstrom
2010-09-14 13:46 ` Mathieu Lonjaret
2010-09-14 13:49 ` Gorka Guardiola
2010-09-14 14:17 ` erik quanstrom
2010-09-15 8:15 ` Mathieu Lonjaret
2010-09-15 9:47 ` roger peppe
2010-09-15 11:07 ` Mathieu Lonjaret
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=1c691961f042c7f6194f62781d377b4e@coraid.com \
--to=quanstro@labs.coraid.com \
--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).