all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: Emacs bugs at the Debian BTS
Date: Wed, 29 Oct 2014 10:57:44 +0000	[thread overview]
Message-ID: <87ioj3b0t3.fsf_-_@violet.siamics.net> (raw)
In-Reply-To: <8k61f398u4.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 28 Oct 2014 17:34:59 -0400")

>>>>> Glenn Morris <rgm@gnu.org> writes:
>>>>> Vincent Lefevre wrote:

	[Dropping Cc: 18851@debbugs.gnu.org.]

[…]

 >> My old bug report in the Debian BTS:

 >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687171

 > IMO there's really no point reporting Emacs problems that aren't
 > specific to Debian (and this issues obviously isn't) to the Debian
 > bug tracker.

	I tend to disagree.  First of all, strictly speaking, there’s no
	easy way for the user to tell if the problem is specific to
	Debian or not, except for building a version of Emacs directly
	from the GNU sources, – and at least /some/ of the Emacs users
	wouldn’t go through the trouble.

	Also (to state the obvious), as it’s the state of the /Debian
	packages/ that Debian BTS tracks, it’s easier to determine if an
	upgrade would resolve any particular issue by looking there,
	rather than at the upstream BTS.

 > They just sit there for some lengthy period of time, and only if they
 > get forwarded here does something happen.  (Although I do look at the
 > Debian Emacs bug reports and had looked at that one.)

	Indeed, that could be improved.  However, anyone’s free to bring
	an issue of their choice to the attention of the upstream
	developers, so that’s just the matter of paying some attention
	to the task.  Perhaps Debian would benefit from reminding the
	users to take these steps on their own (as part of the BTS
	acknowledgment message, for instance), but it seem otherwise an
	obvious thing for an (experienced) user to do, anyway.

[…]

-- 
FSF associate member #7257  np. Фейерверк — Гражданская Оборона … 230E 334A



      parent reply	other threads:[~2014-10-29 10:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 13:33 bug#18851: 24.4; emacs cannot be started if the current directory has been removed Vincent Lefevre
2014-10-28 21:34 ` Glenn Morris
2014-10-29  1:28   ` Vincent Lefevre
2014-10-29  3:50     ` Eli Zaretskii
2014-10-29  8:09       ` Vincent Lefevre
2014-10-29 12:57         ` Stefan Monnier
2014-10-29 14:27           ` Eli Zaretskii
2014-10-29 15:39             ` Vincent Lefevre
2014-10-29 16:07               ` Eli Zaretskii
2014-10-29 16:44                 ` Vincent Lefevre
2014-10-29 16:15               ` Andreas Schwab
2014-10-29 16:51                 ` Vincent Lefevre
2014-10-29 17:31                   ` Andreas Schwab
2014-10-29 17:45                     ` Vincent Lefevre
2014-10-29 18:23                       ` Ivan Shmakov
2014-10-29 21:11                         ` Andreas Schwab
2014-10-30  0:39               ` Stefan Monnier
2015-06-12  0:39                 ` Glenn Morris
2015-06-12  7:53                   ` Eli Zaretskii
2015-06-12 15:45                     ` Glenn Morris
2015-06-12 19:31                       ` Eli Zaretskii
2015-06-13  1:29                         ` Glenn Morris
2015-06-13  7:56                           ` Eli Zaretskii
2015-06-13 23:45                             ` Glenn Morris
2014-10-29 14:23         ` Eli Zaretskii
2014-10-29 15:39           ` Andreas Schwab
2014-10-29 16:00             ` Eli Zaretskii
2014-10-29 16:05           ` Vincent Lefevre
2014-10-29 16:21             ` Eli Zaretskii
2014-10-29  3:40   ` Eli Zaretskii
2014-10-29 10:57   ` Ivan Shmakov [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=87ioj3b0t3.fsf_-_@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=emacs-devel@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.