From: Alexander Dahl <ada@thorsis.com>
To: busybox@busybox.net
Cc: Ron Yorston <rmy@pobox.com>,
vda.linux@googlemail.com, develop@kristov.de,
541544@bugs.debian.org, Jack Bates <ms419@freezone.co.uk>,
dash@vger.kernel.org
Subject: Bug#541544: [PATCH] ash: reset tokpushback before prompting while parsing heredoc
Date: Fri, 23 Nov 2018 15:09:06 +0100 [thread overview]
Message-ID: <1789278.1EysXevFyG@ada> (raw)
In-Reply-To: <5bf482fd.f2mWn8/w5XhV9NAO%rmy@pobox.com>
Hei hei,
I just stumbled over an old entry in the Debian Bug tracker.
Am Dienstag, 20. November 2018, 21:56:13 CET schrieb Ron Yorston:
> Christoph Schulz wrote:
> >I could not reproduce the problem with dash, neither with git dash nor
> >with older versions (0.5.8, 0.5.9.1, 0.5.10.2, to name a few).
> >Something must be handled differently. But I haven't compared busybox
> >ash and dash sources thoroughly either.
>
> The same issue is present in dash and has been discussed in a mailing
> list thread starting here:
>
> https://www.spinics.net/lists/dash/msg01652.html
By chance, is that old Debian Bug here referencing the same problem?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541544
Maybe someone could tell Debian, then?
o.O
Alex
next parent reply other threads:[~2018-11-23 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181111125958.8282-1-develop@kristov.de>
[not found] ` <20181120192142.Horde.sRKu4zTrClxweN4nccD6CkI@localhost>
[not found] ` <5bf482fd.f2mWn8/w5XhV9NAO%rmy@pobox.com>
[not found] ` <20090814183723.7281.91998.reportbug@localhost.localdomain>
2018-11-23 14:09 ` Alexander Dahl [this message]
2018-11-23 14:55 ` Bug#541544: [PATCH] ash: reset tokpushback before prompting while parsing heredoc Ron Yorston
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=1789278.1EysXevFyG@ada \
--to=ada@thorsis.com \
--cc=541544@bugs.debian.org \
--cc=busybox@busybox.net \
--cc=dash@vger.kernel.org \
--cc=develop@kristov.de \
--cc=ms419@freezone.co.uk \
--cc=rmy@pobox.com \
--cc=vda.linux@googlemail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).