From: Kyle Meyer <firstname.lastname@example.org>
Subject: Re: incomplete archives for GitHub issues
Date: Fri, 17 Apr 2020 00:21:53 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
Kyle Meyer <firstname.lastname@example.org> writes:
> Kyle Meyer <email@example.com> writes:
>> There's not _that_ many, so I may make some attempt to fill them in, at
>> least as new mails with links to or quotes of the previous discussion.
> I did a few, but I'll let this be for now.
I did a final pass that should cover nearly all of the remaining ones.
This time I lazily didn't include any quoted text. That's not ideal
because there's discussion that is not captured in this archive, but at
least the reader will know that the conversation is incomplete and that
they should follow a link from one of the messages to see more.
prev parent reply other threads:[~2020-04-17 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 1:45 incomplete archives for GitHub issues Kyle Meyer
2020-04-14 2:23 ` Kyle Meyer
2020-04-17 0:21 ` Kyle Meyer [this message]
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:
List information: https://git.kyleam.com/snakemake-mode
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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).