From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: Adopt a patch!
Date: Fri, 22 Sep 2017 07:02:41 +0200 [thread overview]
Message-ID: <20170922050241.GA15880@thebird.nl> (raw)
In-Reply-To: <87mv5npzdq.fsf@elephly.net>
On Thu, Sep 21, 2017 at 10:31:29PM +0200, Ricardo Wurmus wrote:
> FWIW, I didn’t mean to claim that there are no problems with the
> email-based workflow. I just think that we should improve upon it with
> deliberation instead of jumping to the conclusion that Gitlab or Github
> would be better.
I think we can have both. We are still stuck in this idea that there
should only be one tree. The Linux kernel is proving differently.
Pj.
next prev parent reply other threads:[~2017-09-22 5:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 8:13 Adopt a patch! Ludovic Courtès
2017-09-14 1:22 ` Arun Isaac
2017-09-14 4:26 ` ng0
[not found] ` <4fecd5dd.AEQAQDR72NkAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZudnG@mailjet.com>
2017-09-17 20:04 ` Ludovic Courtès
2017-09-18 10:45 ` Ricardo Wurmus
2017-09-19 14:15 ` Maxim Cournoyer
2017-09-19 14:22 ` Arun Isaac
2017-09-20 5:21 ` Pjotr Prins
2017-09-20 6:11 ` ng0
2017-09-21 9:37 ` Arun Isaac
2017-09-21 11:25 ` Adonay Felipe Nogueira
2017-09-21 16:33 ` ng0
2017-09-20 11:48 ` Hartmut Goebel
2017-09-21 14:08 ` Ricardo Wurmus
2017-09-21 14:39 ` Maxim Cournoyer
2017-09-21 16:16 ` Adonay Felipe Nogueira
2017-09-21 20:31 ` Ricardo Wurmus
2017-09-22 5:02 ` Pjotr Prins [this message]
2017-09-22 12:15 ` Kei Kebreau
2017-09-22 10:42 ` Thomas Danckaert
2017-09-22 14:22 ` Ludovic Courtès
2017-10-14 21:26 ` ng0
2017-09-22 19:45 ` Maxim Cournoyer
2017-09-23 19:51 ` Thomas Danckaert
2017-09-22 9:10 ` Hartmut Goebel
[not found] ` <3db6934a.AEQAQWrlP5MAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZwSg8@mailjet.com>
2017-10-13 13:08 ` 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=20170922050241.GA15880@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--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 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.