From: ng0 <ng0@libertad.pw>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: Patchwork
Date: Thu, 05 May 2016 23:57:31 +0000 [thread overview]
Message-ID: <87lh3odpn8.fsf@libertad.pw> (raw)
In-Reply-To: <87pot4ab2a.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 02 May 2016 14:39:25 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Hello Guix!
>
> Thanks to Siddhesh Poyarekar of glibc & co., Guix patches can now be
> tracked on this Patchwork instance:
>
> http://patchwork.sourceware.org/project/guix/list/
Awesome, thanks!
> Actions can be taken on the Web interface, provided you have an account
> there (I think anyone can create an account on this Patchwork instance.)
I feel a bit uncomfortable registering at webservices which don't
offer tls or .onion, can they extend their existing cert to
patchwork.sourceware.org?
> There’s also a CLI that can perform the read-only actions:
>
> http://patchwork.sourceware.org/project/guix/
>
> (Roughly, it differs from the “patches” in that it’s “Web-first” whereas
> patches is CLI-only.)
>
> Patchwork is subscribed to this mailing list so patches posted on this
> list should appear there as soon as they have been delivered.
>
> I’m not familiar yet with the tool, but I encourage you to give it a
> try and provide feedback.
>
> Happy hacking!
>
> Ludo’.
--
♥Ⓐ ng0
next prev parent reply other threads:[~2016-05-06 0:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 12:39 Patchwork Ludovic Courtès
2016-05-02 15:17 ` Patchwork Ricardo Wurmus
2016-05-02 15:50 ` Patchwork Ludovic Courtès
2016-05-10 6:02 ` Patchwork Efraim Flashner
2016-05-10 13:33 ` Patchwork Ludovic Courtès
2016-05-10 13:56 ` Patchwork Ricardo Wurmus
2016-05-05 23:57 ` ng0 [this message]
2016-05-09 20:38 ` Patchwork Ludovic Courtès
2016-05-09 22:35 ` Patchwork ng0
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=87lh3odpn8.fsf@libertad.pw \
--to=ng0@libertad.pw \
--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 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.