From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: sandeen@sandeen.net, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/3] debian: replace libreadline with libedit
Date: Wed, 20 May 2020 11:18:08 -0700 [thread overview]
Message-ID: <20200520181808.GV17627@magnolia> (raw)
In-Reply-To: <20200520173713.GC1713@infradead.org>
On Wed, May 20, 2020 at 10:37:13AM -0700, Christoph Hellwig wrote:
> On Mon, May 18, 2020 at 05:52:30PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Now that upstream has dropped libreadline support entirely, switch the
> > debian package over to libedit.
>
> Looks good:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> Do we need to resync with the real Debian packaging? That has switched
> over quite a while ago.
It did? It looks to me like debian uses the upstream packaging, even
though they occasionally curse us for doing so.
Now, Ubuntu seems to be doing some sort of valueadd thing around blkid
and "broken configure" but AFAICT they're not sending whatever they
fixed back to us. Party like it's 2005 again.
--D
prev parent reply other threads:[~2020-05-20 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 0:52 [PATCH 0/3] xfsprogs: random fixes Darrick J. Wong
2020-05-19 0:52 ` [PATCH 1/3] xfs_db: don't crash if el_gets returns null Darrick J. Wong
2020-05-19 1:55 ` Eric Sandeen
2020-05-20 17:36 ` Christoph Hellwig
2020-05-19 0:52 ` [PATCH 2/3] xfs_db: fix rdbmap_boundscheck Darrick J. Wong
2020-05-19 1:57 ` Eric Sandeen
2020-05-20 17:36 ` Christoph Hellwig
2020-05-19 0:52 ` [PATCH 3/3] debian: replace libreadline with libedit Darrick J. Wong
2020-05-19 1:58 ` Eric Sandeen
2020-05-20 17:37 ` Christoph Hellwig
2020-05-20 18:18 ` Darrick J. Wong [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=20200520181808.GV17627@magnolia \
--to=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.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