From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Patchwork
Date: Tue, 10 May 2016 09:02:33 +0300 [thread overview]
Message-ID: <20160510060233.GD1075@debian-netbook> (raw)
In-Reply-To: <877ffch32a.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
On Mon, May 02, 2016 at 05:50:21PM +0200, Ludovic Courtès wrote:
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
>
> > I’ve submitted a patch to the mailing list (this time inline with “git
> > send-mail”) and it appeared in the list. Is there any way for us to
> > mark patches as committed via email (e.g. by commenting with something
> > like “Pushed as cabba9e.”) or does patchwork figure this out
> > automatically? Or can only people with an account change the status,
> > and only on the web interface?
>
> That’s a good question! I *think* Patchwork can find out by itself by
> looking at the repository, but I don’t know exactly. We’ll see. :-)
>
> Ludo’.
>
The connman patches I've already committed are still listed as new on patchwork,
and I didn't see a way to manually mark them as done.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-10 6:02 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 ` Efraim Flashner [this message]
2016-05-10 13:33 ` Patchwork Ludovic Courtès
2016-05-10 13:56 ` Patchwork Ricardo Wurmus
2016-05-05 23:57 ` Patchwork ng0
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=20160510060233.GD1075@debian-netbook \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=ludo@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.