From: Nick Buraglio <nick@buraglio.com>
To: "Dave Täht" <davet@teklibre.net>
Cc: Starlink@lists.bufferbloat.net
Subject: Re: [Starlink] starlink disk re-use?
Date: Thu, 3 Feb 2022 09:48:23 -0600 [thread overview]
Message-ID: <CAGB08_fw350n6j==7rTf9z5pVXgd12uypNC4SW7P92nX3LFohg@mail.gmail.com> (raw)
In-Reply-To: <20220202225909.GB2199@mail.taht.net>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
I have someone interested and it was finally nice enough to get it off my
roof. Just need to get it packaged and for the foot and a half of snow to
stop coming down so I can get it shipped. 50F Tuesday, 19F and 12"+ of
snow (and still coming down). Ahh, the midwest.
nb
On Wed, Feb 2, 2022 at 4:59 PM Dave Täht <davet@teklibre.net> wrote:
>
> What did you decide?
>
>
>
[-- Attachment #2: Type: text/html, Size: 712 bytes --]
prev parent reply other threads:[~2022-02-03 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 2:21 Nick Buraglio
2022-01-13 2:36 ` Nathan Owens
2022-01-13 3:10 ` Haudy Kazemi
2022-01-13 6:17 ` Mike Puchol
2022-01-13 20:50 ` Dave Taht
2022-02-02 22:59 ` Dave Täht
2022-02-03 15:48 ` Nick Buraglio [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGB08_fw350n6j==7rTf9z5pVXgd12uypNC4SW7P92nX3LFohg@mail.gmail.com' \
--to=nick@buraglio.com \
--cc=Starlink@lists.bufferbloat.net \
--cc=davet@teklibre.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