From: swedebugia <swedebugia@riseup.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
guix-devel <guix-devel@gnu.org>
Subject: Re: GuixDays: Perfect Setup: Speaker wanted
Date: Sun, 27 Jan 2019 12:09:12 +0100 [thread overview]
Message-ID: <f7d1649f-0d2a-9a39-d23b-7588872253b8@riseup.net> (raw)
In-Reply-To: <87womrch39.fsf@gmail.com>
On 2019-01-26 21:13, Maxim Cournoyer wrote:
> swedebugia <swedebugia@riseup.net> writes:
>
> [...]
>
>> Actually what is even nicer is emacs-debbugs and its ability to apply
>> patches from emails. The UI is somewhat lacking and I think we should
>> fork it so that it defaults to guix bugs and packages.
>
> There's no need to fork emacs-debbugs for that; it's already
> configurable:
>
> (setq debbugs-gnu-default-packages '("guix"))
Thanks for sharing that! I did not look into it deeply and had not
realized this was possible.
I think this should be included in HACKING where emacs-debbugs is mentioned:
"* Using emacs-debbugs
Bug reports and patches are tracked using debbugs. If you are on emacs, you
can use emacs-debbugs.
List all open bug reports on guix-patches with
C-u M-x debbugs-gnu <RET> <RET> guix-patches <RET> n y"
Also we should mention that the error which appears after applying
patches from emails can be ignored - the patches apply succesfully anyways.
If you want to apply only one of several patches from a single email you
have to select manually and run M-x magit-apply (if I remember correctly)
--
Cheers
Swedebugia
next prev parent reply other threads:[~2019-01-27 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 21:31 GuixDays: Perfect Setup: Speaker wanted Björn Höfling
2019-01-25 22:22 ` Pierre Neidhardt
2019-01-26 10:15 ` swedebugia
2019-01-26 20:13 ` Maxim Cournoyer
2019-01-27 11:09 ` swedebugia [this message]
2019-01-27 11:50 ` Ricardo Wurmus
2019-01-29 8:27 ` swedebugia
2019-01-29 11:49 ` Ricardo Wurmus
2019-01-28 12:03 ` Ricardo Wurmus
2019-01-28 14:33 ` swedebugia
2019-01-27 21:56 ` Björn Höfling
2019-01-28 8:38 ` Pierre Neidhardt
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=f7d1649f-0d2a-9a39-d23b-7588872253b8@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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/guix.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.