From: Brian Cully via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: GNU Guix maintainers <guix-maintainers@gnu.org>, guix-devel@gnu.org
Subject: Re: On commit access, patch review, and remaining healthy
Date: Thu, 02 Jun 2022 16:22:51 -0400 [thread overview]
Message-ID: <87ee06g5s4.fsf@ditto.jhoto.spork.org> (raw)
In-Reply-To: <87ee07m77w.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> If you are using Emacs, does debbugs.el have
> shortcomings that make it a problem to review patches?
I’m new to debbugs in general, and Emacs’ debbugs mode in
particular. However, I have been using it to track the status on
some of my patches, or to just generally browse.
There are a few issues:
1) It’d be nice if ‘M-x debbug-guix’ existed. I (briefly) looked
at making such a command, thinking it’d be relatively
straight-forward to just copy ‘debbugs-gnu’ and tweak some
variables, but when it looked like it was going to take more than
10 minutes just to figure out how it was all put together I gave
up as I can’t really dedicate time to it right now.
2) IMHO, the documentation for debbugs is pretty poor. It mostly
relies on GNUS documentation for things like mode help; and while
this makes sense, GNUS is a big, complex package (which is why I
use mu4e instead of it), and it really raises the barrier for
understanding debbugs quite a lot.
3) Even after reading all the documentation I could find, it
doesn’t seem to work very well for an issue-tracker workflow. I
still don’t know how to simply reply to a ticket. Let alone how to
apply a patch to my tree (I did see documentation for how to do
that to the Emacs source tree, but that’s not very useful — also,
the key combinations feel very obtuse and hard for me to
remember).
So, right now, I just use it to browse, since I find it easier
than mumi, but everything else happens with external tools. It’s
very possible my n00b is showing right now and it’s easier to work
with than it seems at first blush, but I’d say that means the
documentation needs some dedicated, non-GNUS-oriented love. It
would be very helpful if there were a HOWTO, like we used to do in
the old days, with how to use it for simple tasks, and stick it in
the info documentation and on the web.
-bjc
next prev parent reply other threads:[~2022-06-02 20:39 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 15:10 On commit access, patch review, and remaining healthy Ludovic Courtès
2022-06-02 20:22 ` Brian Cully via Development of GNU Guix and the GNU System distribution. [this message]
2022-06-03 19:37 ` Ludovic Courtès
2022-06-03 21:17 ` Ricardo Wurmus
2022-06-07 7:08 ` Efraim Flashner
2022-06-07 15:11 ` Ludovic Courtès
2022-06-08 11:39 ` Efraim Flashner
2022-06-08 21:10 ` Ludovic Courtès
2022-06-20 12:53 ` Hartmut Goebel
2022-06-21 15:44 ` zimoun
2022-06-22 9:19 ` Munyoki Kilyungi
2022-06-02 20:32 ` Pier-Hugues Pellerin
2022-06-03 19:42 ` Ludovic Courtès
2022-06-02 21:35 ` Luis Felipe
2022-06-03 8:22 ` Feed on specific topic (public-inbox?) zimoun
2022-06-03 10:51 ` zimoun
2022-06-06 12:11 ` On commit access, patch review, and remaining healthy Arun Isaac
2022-06-06 21:43 ` Ludovic Courtès
2022-06-07 6:44 ` zimoun
2022-06-08 9:30 ` Giovanni Biscuolo
2022-06-14 12:24 ` zimoun
2022-06-15 7:01 ` Arun Isaac
2022-06-15 9:19 ` Ludovic Courtès
2022-06-19 6:55 ` Paul Jewell
2022-06-20 12:11 ` Arun Isaac
2022-06-15 15:11 ` Giovanni Biscuolo
2022-06-08 10:54 ` Giovanni Biscuolo
2022-06-09 19:55 ` Arun Isaac
2022-06-08 9:49 ` Giovanni Biscuolo
2022-06-09 19:50 ` Arun Isaac
2022-06-10 12:27 ` Giovanni Biscuolo
2022-06-10 15:03 ` Efraim Flashner
2022-06-10 16:10 ` Giovanni Biscuolo
2022-06-10 16:26 ` Giovanni Biscuolo
2022-06-10 15:03 ` Maxime Devos
2022-06-11 4:13 ` Thiago Jung Bauermann
2022-06-11 9:37 ` Ludovic Courtès
2022-06-14 11:54 ` zimoun
2022-06-14 15:54 ` Maxim Cournoyer
2022-06-15 6:46 ` Arun Isaac
2022-06-13 12:19 ` Arun Isaac
[not found] <mailman.12124.1654864076.1231.guix-devel@gnu.org>
2022-06-12 8:18 ` Ricardo Wurmus
2022-06-12 9:42 ` Giovanni Biscuolo
2022-06-12 13:10 ` Maxime Devos
2022-06-13 9:34 ` Giovanni Biscuolo
2022-06-13 10:48 ` Maxime Devos
2022-06-13 14:21 ` Giovanni Biscuolo
2022-06-12 8:21 ` Ricardo Wurmus
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ee06g5s4.fsf@ditto.jhoto.spork.org \
--to=guix-devel@gnu.org \
--cc=bjc@spork.org \
--cc=guix-maintainers@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).