public inbox for
 help / color / mirror / Atom feed
From: Brian Inglis <>
Subject: Re: [ITA] ncurses
Date: Thu, 26 May 2022 19:28:25 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2022-05-26 13:35, Jon Turney wrote:
> On 23/05/2022 06:13, Brian Inglis wrote:
>> I'd like to adopt orphaned package ncurses:
>> The builds were tested in GitHub Actions CI using the scallywag ncurses
>> repo playground branch; see:
> Thanks.
> Unfortunately, this crossed with a NMU of ncurses that I did recently, 
> so I don't know what you want to do about that.

No problem. I've been working on playground. I'll pull master and merge.

> I added this to your authorized packages.


Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2022-05-27  1:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23  5:13 Brian Inglis
2022-05-26 19:35 ` Jon Turney
2022-05-27  1:28   ` Brian Inglis [this message]
2022-05-27  5:16     ` Brian Inglis
2022-05-28 12:02       ` Jon Turney

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:

* 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.
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).