From: swedebugia <swedebugia@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: GuixDays: Perfect Setup: Speaker wanted
Date: Mon, 28 Jan 2019 15:33:17 +0100 [thread overview]
Message-ID: <5C87C24E-D65B-4008-A560-AE91D71E74BC@riseup.net> (raw)
In-Reply-To: <87sgxdq99d.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
Ricardo Wurmus <rekado@elephly.net> skrev: (28 januari 2019 13:03:42 CET)
>
>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.
>
>FWIW you don’t need emacs-debbugs to apply patches from emails, nor do
>you need emacs-debbugs at all if you don’t want to use it.
>
>At https://issues.guix.info you can download any message by clicking on
>the “Download” link in the upper right corner. You can download
>individual parts of multipart messages. You can then apply any
>downloaded patches with “git am”.
>
>--
>Ricardo
I will return with the error message.
I liked that it makes it easier to apply and review patches.
I know that it can be done manually but that's cumbersome in my view.
--
Sent from my k-9 mail for Android.
[-- Attachment #2: Type: text/html, Size: 1425 bytes --]
next prev parent reply other threads:[~2019-01-28 14:33 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
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 [this message]
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
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=5C87C24E-D65B-4008-A560-AE91D71E74BC@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).