From: Nils Gillmann <niasterisk@grrlz.net>
To: guix-devel@gnu.org
Subject: Re: [REQ/DISCUSSION] patch managing system
Date: Mon, 21 Mar 2016 14:58:27 +0100 [thread overview]
Message-ID: <87d1qogcfw.fsf@grrlz.net> (raw)
In-Reply-To: 87h9g0eq1c.fsf@grrlz.net
First follow up idea:
Ideal case would be:
- integration with Guix in the future (the emacs interface and
other potential future interfaces)
- integration into Guix website
- patches can be marked:
- state (done/open)
- priority
- patches can be assigned to more than 1 person
- webinterface
As we are not at the ideal case and need a software until we get
there, most projects seem to either use mailman, bugzilla,
something equal to prmon.freebsd.org (ports monitor), simple pull
requests on a mirror on a bigger source control system.
what are your thoughts?
--
ng
personal contact: http://krosos.sdf.org
EDN: https://wiki.c3d2.de/EDN
next prev parent reply other threads:[~2016-03-21 13:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 22:35 [REQ/DISCUSSION] patch managing system Nils Gillmann
2016-03-21 13:58 ` Nils Gillmann [this message]
2016-03-21 14:15 ` Ricardo Wurmus
2016-03-21 14:34 ` Nils Gillmann
2016-03-21 15:10 ` Nils Gillmann
2016-03-21 16:43 ` Ludovic Courtès
2016-03-22 11:53 ` Nils Gillmann
2016-03-22 16:26 ` Ludovic Courtès
2016-03-23 4:44 ` Chris Marusich
2016-03-23 7:41 ` Ricardo Wurmus
2016-03-23 8:15 ` Chris Marusich
2016-03-23 8:57 ` Andy Wingo
2016-03-23 8:36 ` Alex Kost
2016-03-23 8:54 ` Chris Marusich
2016-03-23 22:24 ` Ludovic Courtès
2016-03-24 8:53 ` Alex Kost
2016-03-23 16:02 ` Leo Famulari
2016-04-16 11:13 ` Ludovic Courtès
2016-04-28 8:24 ` Patch tracking Ludovic Courtès
2016-04-28 11:30 ` Ben Woodcroft
2016-04-28 12:17 ` Ludovic Courtès
2016-05-02 8:25 ` Ricardo Wurmus
2016-03-21 15:48 ` [REQ/DISCUSSION] patch managing system Mathieu Lirzin
2016-03-21 16:08 ` Mathieu Lirzin
2016-03-30 20:52 ` Cyril Roelandt
2016-03-31 6:39 ` Efraim Flashner
2016-03-31 7:53 ` 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=87d1qogcfw.fsf@grrlz.net \
--to=niasterisk@grrlz.net \
--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).