From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <d@taht.net>
Received: from mainmail.teklibre.com (mainmail.teklibre.org
	[IPv6:2001:4f8:3:36:2e0:81ff:fe23:90d3])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "mainmail.teklibre.com",
	Issuer "CA Cert Signing Authority" (verified OK))
	by lists.bufferbloat.net (Postfix) with ESMTPS id 89F502E03AD
	for <bismark-devel@lists.bufferbloat.net>;
	Wed, 20 Apr 2011 15:25:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by mainmail.teklibre.com (Postfix) with ESMTP id C04AC3DA139
	for <bismark-devel@lists.bufferbloat.net>;
	Wed, 20 Apr 2011 15:59:41 -0700 (PDT)
Received: from mainmail.teklibre.com ([127.0.0.1])
	by localhost (toutatis.sql1.isc.org [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id YpAHm5Wx06MI for <bismark-devel@lists.bufferbloat.net>;
	Wed, 20 Apr 2011 15:59:41 -0700 (PDT)
Received: from [192.168.1.116] (c-98-229-99-32.hsd1.ma.comcast.net
	[98.229.99.32])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate) (Authenticated sender: d)
	by mainmail.teklibre.com (Postfix) with ESMTPSA id 364543DA121
	for <bismark-devel@lists.bufferbloat.net>;
	Wed, 20 Apr 2011 15:59:41 -0700 (PDT)
Message-ID: <4DAF5D39.4010206@taht.net>
Date: Wed, 20 Apr 2011 16:24:57 -0600
From: Dave Taht <d@taht.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: bismark-devel@lists.bufferbloat.net
References: <3BFD72FA-D352-4B3C-A743-6393A77603B8@cc.gatech.edu>
	<4DAF4F0E.6080909@taht.net> <4DAF5A4D.5020804@taht.net>
	<FA33A96D-2A33-4975-9FFF-8584D4D9FB86@cc.gatech.edu>
In-Reply-To: <FA33A96D-2A33-4975-9FFF-8584D4D9FB86@cc.gatech.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Bismark-devel] Bismark flash success! + 5 GHz radio issue
X-BeenThere: bismark-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: BISMark related software development
	<bismark-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bismark-devel>,
	<mailto:bismark-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bismark-devel>
List-Post: <mailto:bismark-devel@lists.bufferbloat.net>
List-Help: <mailto:bismark-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bismark-devel>,
	<mailto:bismark-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Wed, 20 Apr 2011 22:25:00 -0000

On 04/20/2011 04:14 PM, Nick Feamster wrote:
> Cool... I'll change instructions.  Just wanted to run my experience by folks first (and for my own benefit, before I forgot :-)

On a wiki, it is always better to ask forgiveness than permission.

(and I note that only people that are registered on the website as 
contributors or higher to this project have write access to the bismark 
wiki)

You can "watch" certain pages...

And you can also passively subscribe to several RSS feeds, if you like 
RSS feeds, to see changes go by.

I use sometimes rss2email to do that myself (this is better for blog 
postings than this purpose, under Linux, for example, liferea is pretty 
good. Here's how I keep track of all activities going on, after clicking 
on the wiki edit checkbox on the activities page:

http://www.bufferbloat.net/projects/bismark/activity

http://www.bufferbloat.net/projects/bismark/activity.atom?key=fd2181feb4c417f4dd140e1a3e64a8f11e4de234&show_changesets=1&show_documents=1&show_files=1&show_issues=1&show_news=1&show_wiki_edits=1

You can filter down significantly as well.

For new issues, you can subscribe to various feeds (or I can add you to 
the mailing list)

http://www.bufferbloat.net/projects/bloat/issues.atom

http://www.bufferbloat.net/projects/bismark/issues.atom

And so on.

Email is GREAT, as are searchable archives of email, but...