unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-tangents@gnu.org, stephen_leake@stephe-leake.org,
	john@yates-sheets.org
Subject: Re: Too few people taking care of bug reports, was: Re: Release	process (was Re: Move to a cadence release model?)
Date: Wed, 11 Nov 2015 23:42:53 +0200	[thread overview]
Message-ID: <83a8qkjjqa.fsf@gnu.org> (raw)
In-Reply-To: <5643B1E1.5040605@yandex.ru>

> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Wed, 11 Nov 2015 23:23:45 +0200
> Cc: emacs-tangents@gnu.org, stephen_leake@stephe-leake.org,
> 	john@yates-sheets.org
> 
> > I disagree.  IME, frequently just looking or stepping through
> > unfamiliar code can reveal bugs whose reasons we can easily understand
> > and fix.  Just a few minutes ago I had this experience once more, see
> > bug#21881.  I assure you I knew nothing at all about mm-url.el, and
> > still don't.  Still, it took me just a few minutes to understand why
> > EWW barfs and see the solution that I'm sure is right.
> 
> I'm not saying I couldn't do that, but there's a limit to the number of 
> areas I want to be familiar with. I also have limited of time and other 
> projects, starving for attention.
> 
> I'm also currently exhausted by trying to explain the difference between 
> "project" and "libraries", to some people, over a zillion email messages.
> 
> > You should try this some time.  I think everybody here should.
> 
> The above is the primary method I do get acquainted with new code.
> 
> > Bottom line is: people like you and me (and many others here) know
> > quite a lot about Emacs and about debugging, and can find solutions to
> > many bugs even in unfamiliar code.
> 
> Been there, done that. Especially in third-party code, where it's much 
> easier to discuss the issues, explore the code, etc, everything without 
> closing the browser.

Then it sounds like you agree with me, and we both are doing about the
bugs whatever we can, given our free resources.  Thanks, and please
keep up.



  parent reply	other threads:[~2015-11-11 21:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJnXXogfOJEO3fbiVnE-v3q_KAM71wO_YUw7NBehwTE4S1SMsQ@mail.gmail.com>
     [not found] ` <m2611ahqtq.fsf@Vulcan.attlocal.net>
     [not found]   ` <8337wdn6uu.fsf@gnu.org>
     [not found]     ` <m26119bxcj.fsf@Vulcan.attlocal.net>
     [not found]       ` <86611975jo.fsf_-_@stephe-leake.org>
     [not found]         ` <838u65kxly.fsf@gnu.org>
     [not found]           ` <86mvuk4xxd.fsf@stephe-leake.org>
     [not found]             ` <831tbwlext.fsf@gnu.org>
2015-11-11 20:39               ` Too few people taking care of bug reports, was: Re: Release process (was Re: Move to a cadence release model?) Dmitry Gutov
2015-11-11 20:50                 ` Too few people taking care of bug reports, John Wiegley
2015-11-11 21:03                   ` Dmitry Gutov
2015-11-11 21:06                     ` John Wiegley
2015-11-11 21:14                   ` Eli Zaretskii
2015-11-11 21:10                 ` Too few people taking care of bug reports, was: Re: Release process (was Re: Move to a cadence release model?) Eli Zaretskii
2015-11-11 21:15                   ` Too few people taking care of bug reports, John Wiegley
2015-11-11 21:27                     ` Eli Zaretskii
2015-11-11 21:23                   ` Too few people taking care of bug reports, was: Re: Release process (was Re: Move to a cadence release model?) Dmitry Gutov
2015-11-11 21:30                     ` Eli Zaretskii
2015-11-11 21:31                       ` Dmitry Gutov
2015-11-11 21:42                     ` Eli Zaretskii [this message]
2015-11-11 21:54                       ` Dmitry Gutov

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=83a8qkjjqa.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-tangents@gnu.org \
    --cc=john@yates-sheets.org \
    --cc=stephen_leake@stephe-leake.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 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).