From: Marcin Borkowski <mbork@mbork.pl>
To: Emacs Devel <emacs-devel@gnu.org>
Subject: A problem with old bugs
Date: Wed, 01 Mar 2017 09:22:55 +0100 [thread overview]
Message-ID: <87r32h9zj4.fsf@jane> (raw)
Hi there,
I'm sorry to say that I'm a bit sad. A few months ago (maybe a year)
there was a call to so some work on old, outstanding bugs.
I volunteered for that, and while I did not spend /a lot/ of time on
that, I feel that I did indeed help a bit. Then, I proceeded to
actually fix a few bugs that were within my reach. I sent a patch
fixing 21072, then a patch fixing one bug I did not formally submit (but
both the bug and the patch are seemingly quite trivial), and then wanted
to start discussion on 19873.
Unfortunately, I have to say that I got very little feedback. There was
some discussion (John's on testing, Eli's on my stupid mistakes etc.),
but my patches/emails are mainly left there undecided.
I do understand the main reason (too few developers, the bugs were not
critical), but I have to say that the situation isn't exactly motivating
for me. I will try to continue work on some bugs for the next week or
two, but I guess I'll stop then, since at this moment it doesn't feel to
have a lot of sense anyway, and I have a lot of ways to spend my time in
a meaningful way...
Is there anything that could be done to avoid turning off people wanting
to help with Emacs development? Did I choose wrong bugs to work on? If
so, should I close them as "wontfix", even though (in 2 cases) there are
actual patches that seem to fix them?
Best,
--
Marcin Borkowski
next reply other threads:[~2017-03-01 8:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 8:22 Marcin Borkowski [this message]
2017-03-01 10:26 ` A problem with old bugs Thien-Thi Nguyen
2017-03-01 13:28 ` Marcin Borkowski
2017-03-02 7:38 ` Thien-Thi Nguyen
2017-03-02 12:33 ` Noam Postavsky
2017-03-02 16:53 ` Richard Stallman
2017-03-07 6:17 ` Marcin Borkowski
2017-03-06 13:19 ` Phillip Lord
2017-03-07 6:16 ` Marcin Borkowski
2017-03-07 12:24 ` Phillip Lord
2017-03-01 16:16 ` Eli Zaretskii
2017-03-07 6:15 ` Marcin Borkowski
2017-03-07 16:51 ` Eli Zaretskii
2017-03-08 7:01 ` Marcin Borkowski
2017-03-08 16:08 ` Eli Zaretskii
2017-05-21 16:00 ` John Wiegley
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=87r32h9zj4.fsf@jane \
--to=mbork@mbork.pl \
--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.