all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: guix-devel@gnu.org
Subject: Re: [REQ/DISCUSSION] patch managing system
Date: Tue, 22 Mar 2016 17:26:52 +0100	[thread overview]
Message-ID: <8760wetr5f.fsf@gnu.org> (raw)
In-Reply-To: <87egb2ybhy.fsf@grrlz.net> (Nils Gillmann's message of "Tue, 22 Mar 2016 12:53:45 +0100")

Nils Gillmann <niasterisk@grrlz.net> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hi!
>>
>> The best patch-tracking candidate I’ve seen so far is “patches”, written
>> by/for the QEMU people (the ‘patches’ package in Guix.)
>>
>>   https://www.gnu.org/software/guix/packages/#patches
>>
>> I think it has everything most of us want, including an Emacs interface.
>>
>> The main “difficulty” is setting it up on a machine where it can serve
>> those patches.json files over HTTP based on the mailing list archive
>> (which could be synced from <ftp://lists.gnu.org/guix-devel/>) and Git
>> repo.  There’s a README in the the source tree that explains the
>> details:
>>
>>   https://github.com/aliguori/patches/blob/master/README-server.md
>>
>> Would someone like to set it up somewhere and share a recipe?  I’d be
>> happy to beta-test it as soon as it’s available!  :-)
>>
>> Ludo’.
>
> Yesterday I got my domains moved back into their old place, so I
> will try to read into this and see if I can setup a system
> dedicated to this so we could test it.

Awesome, thank you!

Ludo’.

  reply	other threads:[~2016-03-22 16:27 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8760wetr5f.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=niasterisk@grrlz.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.