From: Edgar Lee <edgarhinshunlee@gmail•com>
To: Vincent Ambo <mail@tazj•in>
Cc: depot@tvl.su
Subject: Re: Nixery + nix-snapshotter
Date: Mon, 11 Sep 2023 22:13:30 -0400 [thread overview]
Message-ID: <CALK74L6gFBcMFn3UgV8BWXejL1Xmx5+SYdjkM+vLAVy+s2=8WQ@mail.gmail.com> (raw)
In-Reply-To: <CANHrikpMVhb_9ALpuLdU+eGiimEpeHUB7cnSBgE4KRNnz5bcnw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
Hi Vincent,
Sounds good, let’s chat over a call first. Here are my availabilities:
Tues Sept 12, 9-9:45am, 10-11:30am EST
Thurs Sept 14, 10-12pm EST
Fri Sept 15, 10:30-12pm EST
Best,
Edgar
On Mon, Sep 11, 2023 at 5:18 PM Vincent Ambo <mail@tazj•in> wrote:
> Hey Edgar!
>
> Responding to your IRC message here, as it seems you've dropped off the
> network. I've CC'd in depot@tvl.su, which makes this conversation public
> in our public inbox at https://inbox.tvl.su
>
> For context: https://github.com/tazjin/nixery/issues/160
>
> > <hinshun> i'm UTC-4, [...]. otherwise the only reasonable time is my
> > 9am - your 4pm.
>
> Sleep off your jetlag first, no rush! I tend to start working pretty
> late, and finish pretty late, so consider me available until ~8pm my
> time (i.e. 1pm your time). Async also works, though I find a quick call
> is usually more productive to kick things off.
>
> To start with: It's not clear to me what kind of image would need to be
> served by Nixery. I suspect it's related to the "remote snapshotter"
> feature, and we'd need to serve the individual derivations as image
> layers with some kind of metadata?
>
> //V
>
[-- Attachment #2: Type: text/html, Size: 2016 bytes --]
prev parent reply other threads:[~2023-09-12 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 21:18 Vincent Ambo
2023-09-12 2:13 ` Edgar Lee [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALK74L6gFBcMFn3UgV8BWXejL1Xmx5+SYdjkM+vLAVy+s2=8WQ@mail.gmail.com' \
--to=edgarhinshunlee@gmail$(echo .)com \
--cc=depot@tvl.su \
--cc=mail@tazj$(echo .)in \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://code.tvl.fyi
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 read-only IMAP folder(s) and NNTP newsgroup(s).