From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14002@debbugs.gnu.org
Subject: bug#14002: 24.3.50; buffer-file-coding-system is undecided-dos, everywhere
Date: Thu, 21 Mar 2013 00:40:44 +0400 [thread overview]
Message-ID: <514A1ECC.7080006@yandex.ru> (raw)
In-Reply-To: <83y5diypt7.fsf@gnu.org>
On 20.03.2013 20:54, Eli Zaretskii wrote:
>> Date: Wed, 20 Mar 2013 08:18:23 +0400
>> From: Dmitry Gutov <dgutov@yandex.ru>
>> CC: 14002@debbugs.gnu.org,
>> GNU bug tracker automated control server <control@debbugs.gnu.org>
>>
>>> (Why don't people try to look for similar bug reports before they do?)
>>
>> Obviously, you only notice the cases when they don't.
>
> Obviously. But the point is, there are too many of those duplicates.
Given the size of Emacs user community, I'd rather expect more bug
reports, including duplicate, nonsensical, etc, than currently.
In this specific case, I though I'm aware of the current bugs (I'm
subscribed to gmane.emacs.bugs in Gnus), and I also thought that this
kind of bug wouldn't stay unfixed for more than a day, much less 5 days
that went since 13977 was filed. I was wrong on both counts.
Speaking of bug reports, the recent font-lock breakage was similar in
that it was obvious and stayed unfixed for a while. It just affected a
bigger audience.
prev parent reply other threads:[~2013-03-20 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 2:26 bug#14002: 24.3.50; buffer-file-coding-system is undecided-dos, everywhere Dmitry Gutov
[not found] ` <handler.14002.B.136374651732012.ack@debbugs.gnu.org>
2013-03-20 2:39 ` bug#14002: Acknowledgement (24.3.50; buffer-file-coding-system is undecided-dos, everywhere) Dmitry Gutov
2013-03-20 4:05 ` bug#14002: 24.3.50; buffer-file-coding-system is undecided-dos, everywhere Eli Zaretskii
2013-03-20 4:18 ` Dmitry Gutov
2013-03-20 16:54 ` Eli Zaretskii
2013-03-20 20:40 ` Dmitry Gutov [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=514A1ECC.7080006@yandex.ru \
--to=dgutov@yandex.ru \
--cc=14002@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.