unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: L  p R n  d n    <guix@lprndn.info>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34189@debbugs.gnu.org
Subject: [bug#34189] [PATCH] gnu: Add arcan.
Date: Mon, 18 Mar 2019 12:02:16 +0100	[thread overview]
Message-ID: <cuck1gwzbrb.fsf@lprndn.info> (raw)
In-Reply-To: <877ecwr0a3.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 18 Mar 2019 10:37:24 +0100")

Hello,

Ludovic Courtès <ludo@gnu.org> writes:

> Hello,
>
> L  p R n  d n    <guix@lprndn.info> skribis:
>
>> I join new patches for xarcan and arcan-wayland.
>
> Perfect, I’ve applied both!
>
> Are we done?
>
> Thank you,
> Ludo’.


Sorry, there are still aclip, aloadimage and durden. I didn't send a new
patch because they were not impacted by the previous changes. Do you
want me to send them again?

Thank you very much!

Lprndn

      reply	other threads:[~2019-03-18 10:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 12:54 [bug#34189] [PATCH] gnu: Add arcan L p R n d n
     [not found] ` <handler.34189.B.154833088612044.ack@debbugs.gnu.org>
2019-01-24 12:57   ` [bug#34189] Acknowledgement ([PATCH] gnu: Add arcan.) L p R n d n
2019-01-24 12:58   ` L p R n d n
2019-01-24 12:58   ` L p R n d n
2019-01-24 12:59   ` L p R n d n
2019-01-24 12:59   ` L p R n d n
2019-01-24 12:59   ` L p R n d n
2019-02-06 21:32 ` [bug#34189] [PATCH] gnu: Add arcan Ludovic Courtès
     [not found]   ` <cucwombb7y5.fsf@lprndn.info>
2019-02-09 21:42     ` Ludovic Courtès
2019-02-10 18:49       ` L p R n d n
2019-03-04 14:10         ` Ludovic Courtès
2021-07-13 13:15           ` bug#34189: " Maxim Cournoyer
2019-03-13 11:20 ` [bug#34189] " L p R n d n
2019-03-18  9:37   ` Ludovic Courtès
2019-03-18 11:02     ` L p R n d n [this message]

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=cuck1gwzbrb.fsf@lprndn.info \
    --to=guix@lprndn.info \
    --cc=34189@debbugs.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 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).