user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Ali Alnubani <alialnu@nvidia.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: stable 1.6.1 release? [was: [PATCH] eml: fix undefined vars on <Perl 5.28]
Date: Thu, 31 Dec 2020 00:06:18 +0000	[thread overview]
Message-ID: <20201231000618.GA17243@dcvr> (raw)
In-Reply-To: <20201226203528.GA9786@dcvr>

Eric Wong <e@80x24.org> wrote:
> Ali Alnubani <alialnu@nvidia.com> wrote:
> > I no longer see the uninitialized value warnings or the test
> > failure on Debian 9 with both patches applied on master. Do
> > you plan on creating a new release tag soon with these fixes?
> 
> Thanks, pushed to master and I've started a stable-1.6 branch
> to https://80x24.org/public-inbox.git with 29 commits
> cherry-picked from master which I hope are suitable.
> 
> There's two more I'm tempted to cherry-pick, though they
> introduce behavior changes:
> 
>   fe01d7b117c8b1e1 import: drop X-Status in addition to Status

I've picked fe01d7b117c8b1e1 since it's a potential privacy leak.

>   1bf653ad139bf7bb nntp+www: drop List-* and Archived-At headers

Doesn't apply cleanly, but trivial to fix.  But not sure if it's
a big-enough issue.  Anyways, I'll release 1.6.1 before 2021...

(still lots of stuff brewing for lei + extindex...)

  reply	other threads:[~2020-12-31  0:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-26 11:27 [Debian 9][Perl 5.24] uninitialized value errors in Encode/MIME/Header.pm Ali Alnubani
2020-12-26 12:25 ` [PATCH] eml: fix undefined vars on <Perl 5.28 Eric Wong
2020-12-26 14:10   ` Ali Alnubani
2020-12-26 20:35     ` stable 1.6.1 release? [was: [PATCH] eml: fix undefined vars on <Perl 5.28] Eric Wong
2020-12-31  0:06       ` Eric Wong [this message]
2020-12-26 12:30 ` [PATCH] t/config: test --get-urlmatch for git <2.26 Eric Wong
2020-12-26 14:12   ` Ali Alnubani

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://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201231000618.GA17243@dcvr \
    --to=e@80x24.org \
    --cc=alialnu@nvidia.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=meta@public-inbox.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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