From: Ricardo Wurmus <rekado@elephly.net>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: gnu-patches back log
Date: Tue, 07 Mar 2017 13:09:50 +0100 [thread overview]
Message-ID: <87shmp2sq9.fsf@elephly.net> (raw)
In-Reply-To: <CAJ98PDxXP2BjOf8b+19w6RR=ZAErYySo2z=0kZebAN-VLkSBZA@mail.gmail.com>
Catonano <catonano@gmail.com> writes:
> Wrapping up, I think 2 interesting ideas popped up in this thread
>
> One is the automation of building of new packages patches
I wouldn’t know how to set this up. Hydra isn’t powerful enough for our
*current* purposes, so I wouldn’t want to increase the load at this
point.
> Another one is the weekly report about pending patches and merged
>patches
I’d rather not have a weekly report (I get enough email through the
various Guix mailing lists already). The debbugs interface shows all
open patches already. (We should get more people to use guix-patches
instead of guix-devel, though.)
Other than that I’d like to second everything Leo has written.
I agree with Pjotr that obviously it would be nice to have faster/more
reviews/mentoring. That’s something everybody can help with, even if it
is just a matter of reviewing licenses or trying to build or run the
package. But this all falls apart under stress (speaking from
experience here), so it’s best not to force it.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-03-07 12:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 14:21 How to M-x debbugs-gnu with new guix-patches Christopher Allan Webber
2017-02-22 17:26 ` Catonano
2017-02-26 11:10 ` Pjotr Prins
2017-02-26 19:02 ` Christopher Allan Webber
2017-02-28 6:25 ` gnu-patches back log Pjotr Prins
2017-02-28 11:14 ` Hartmut Goebel
2017-03-01 5:23 ` Pjotr Prins
2017-03-01 6:16 ` Leo Famulari
2017-03-01 8:17 ` Pjotr Prins
2017-03-01 10:42 ` Andy Wingo
2017-03-01 11:17 ` Pjotr Prins
2017-03-01 12:48 ` Thomas Danckaert
2017-03-01 15:06 ` Pjotr Prins
2017-03-01 13:14 ` Leo Famulari
2017-03-01 14:45 ` Pjotr Prins
2017-03-01 15:51 ` Leo Famulari
2017-03-01 16:07 ` Pjotr Prins
2017-03-01 23:08 ` Catonano
2017-03-07 12:09 ` Ricardo Wurmus [this message]
2017-03-13 17:37 ` Catonano
2017-03-01 14:16 ` ng0
2017-03-01 13:14 ` John Darrington
2017-03-06 16:14 ` Ludovic Courtès
2017-03-07 11:44 ` Hartmut Goebel
2017-03-11 21:30 ` Ludovic Courtès
2017-03-25 12:37 ` How to M-x debbugs-gnu with new guix-patches Catonano
2017-03-25 21:45 ` Ludovic Courtès
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=87shmp2sq9.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=catonano@gmail.com \
--cc=guix-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 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).