From: Leo Famulari <leo@famulari.name>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: gnu-patches back log
Date: Wed, 1 Mar 2017 10:51:14 -0500 [thread overview]
Message-ID: <20170301155114.GA18568@jasmine> (raw)
In-Reply-To: <20170301144551.GA12261@mail.thebird.nl>
On Wed, Mar 01, 2017 at 02:45:51PM +0000, Pjotr Prins wrote:
> OK. I was not planning to badger ;). Sometimes describing a problem
> can be valuable. Feel free to ignore. We all have different itches
> to scratch. I'll shut up again.
Okay, I really don't want you to shut up. As you say, we all have our
own itches to scratch (my phrase is "motivation is not fungible"), and
Guix should try to make use of everyone's energy.
But I got the impression (probably mistaken) that you felt the
committers / reviewers were choosing to spurn contributions, and it
really bothered me. Like I said, many of us are giving as much time and
energy as we can.
next prev parent reply other threads:[~2017-03-01 15:51 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 [this message]
2017-03-01 16:07 ` Pjotr Prins
2017-03-01 23:08 ` Catonano
2017-03-07 12:09 ` Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170301155114.GA18568@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.