From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Olof Johansson <olof.johansson@axis.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] coreutils: revert upstream commit causing havoc with ls output
Date: Mon, 23 May 2016 14:09:09 -0400 [thread overview]
Message-ID: <20160523180908.GE27984@windriver.com> (raw)
In-Reply-To: <20160521101858.GP21318@axis.com>
[Re: [OE-core] [PATCH] coreutils: revert upstream commit causing havoc with ls output] On 21/05/2016 (Sat 12:18) Olof Johansson wrote:
> On 16-05-20 20:02 -0400, Paul Gortmaker wrote:
> > Several large distros are voting with their feet and actively
> > reverting the change, as per what can be seen above for Debian.
>
> To me, it sounds like you're saying that the Debian maintainer is
> actively taking a stand against upstream, but the changelog makes
> it sound more like a temporary thing.
I did write "... it doesn't appear that the coreutils folks are going
to change the default back to the old way..."
>
> From the changelog entry:
> > * Disable default ls quoting for now to get the rest of 8.25
> > into testing. (Closes: #813164)
>
> Could you add something in the commit message to make this
> clearer?
I suppose I can resend with "..coreutils folks are _ever_ going to..."
if you think that extra word clarifies things in the OE log I wrote.
The log of the actual patch is as-is from Debian, aside from me adding
the Upstream-Status, the http source and my SOB line. Is that the log
you were hoping to have added to/clarified?
Paul.
--
>
> --
> olofjn
next prev parent reply other threads:[~2016-05-23 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 0:02 [PATCH] coreutils: revert upstream commit causing havoc with ls output Paul Gortmaker
2016-05-21 10:18 ` Olof Johansson
2016-05-23 18:09 ` Paul Gortmaker [this message]
2016-05-24 7:35 ` Olof Johansson
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=20160523180908.GE27984@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=olof.johansson@axis.com \
--cc=openembedded-core@lists.openembedded.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.