From: "Jan Djärv" <jan.h.d@swipnet.se>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: 6535@debbugs.gnu.org, john ffitch <jpff@codemist.co.uk>
Subject: bug#6535: 24.0.50; grep seems not to work
Date: Tue, 29 Jun 2010 17:52:39 +0200 [thread overview]
Message-ID: <4C2A16C7.2020709@swipnet.se> (raw)
In-Reply-To: <876312t7iz.fsf@gmail.com>
Štěpán Němec skrev 2010-06-29 13.14:
>
> Nothing suggests anyone is working on fixing the problem. If you have a
> fix, why don't you commit it?
I don't have a recepie for repeating the problem turning off ICANON would
solve. It isn't a high priority for me.
> If you don't have a fix *now*, why is the
> breakage not reverted for the time being? I didn't even get any reaction
> on this question.
That you must ask the person who made that checkin.
>
> I don't expect the trunk to be perfectly usable all the time, but I fail
> to see any value in leaving a known and repeatedly reported breakage in
> for an extended period of time.
>
The breakage must have fixed some other problem. If breakage one is better
than breakage two is a matter of opinion, depending which one you see the
most. AFAIK, I haven't seen either.
Jan D.
next prev parent reply other threads:[~2010-06-29 15:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 16:59 bug#6535: 24.0.50; grep seems not to work john ffitch
2010-06-29 8:31 ` Štěpán Němec
2010-06-29 9:43 ` Jan Djärv
2010-06-29 11:14 ` Štěpán Němec
2010-06-29 15:52 ` Jan Djärv [this message]
2010-06-29 18:27 ` Štěpán Němec
2010-06-30 11:47 ` Jan Djärv
2010-06-29 9:38 ` Jan Djärv
2010-06-29 10:10 ` john ffitch
2010-06-29 10:41 ` Jan Djärv
2010-06-29 11:03 ` root
2010-06-29 12:24 ` Jan Djärv
2010-06-29 16:57 ` Juri Linkov
2010-06-29 18:09 ` Jan Djärv
2010-06-29 19:19 ` john ffitch
2010-06-30 8:16 ` Juri Linkov
2010-06-30 9:32 ` Jan Djärv
2010-06-29 12:09 ` Jan Djärv
2011-09-21 21:07 ` Lars Magne Ingebrigtsen
2011-09-22 8:52 ` john ffitch
2011-09-23 8:34 ` Lars Magne Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C2A16C7.2020709@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=6535@debbugs.gnu.org \
--cc=jpff@codemist.co.uk \
--cc=stepnem@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).