all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <raghavgururajan@disroot.org>
To: "Pierre Neidhardt" <mail@ambrevar.xyz>,
	"Nicolò Balzarotti" <anothersms@gmail.com>,
	41134@debbugs.gnu.org
Subject: [bug#41134] [PATCH 2/2] gnu: Add libappindicator.
Date: Mon, 11 May 2020 10:18:19 -0400	[thread overview]
Message-ID: <3d720723-7dac-1ab1-0c04-d9b7818a6511@disroot.org> (raw)
In-Reply-To: <87pnbaactg.fsf@ambrevar.xyz>


[-- Attachment #1.1.1: Type: text/plain, Size: 489 bytes --]

Hi Pierre!

> Actually you've got blueman here to, as in 41025@debbugs.gnu.org.
> Raghav, Nicolò, what do you think?  Which is one is more complete?

Pierre:
I'd say, let us go with dbus-test-runner from Nicolò's 4113#4;
libindicator+libappindicator from yours' 41143#0 and 4113#1; blueman
from my 41025#14.
So if you could update libindicator and libappindicator, by using
dbus-test-runner; I can update blueman to integrate them. Wdyt?

Nicolò:
Wdyt?

Regards,
RG.


[-- Attachment #1.1.2: 0xAE6EF3046D6F7B57.asc --]
[-- Type: application/pgp-keys, Size: 2877 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-05-11 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08  6:34 [bug#41134] [PATCH 1/2] gnu: Add libindicator Pierre Neidhardt
     [not found] ` <handler.41134.B.158891966521951.ack@debbugs.gnu.org>
2020-05-08  6:42   ` [bug#41134] [PATCH 2/2] gnu: Add libappindicator Pierre Neidhardt
2020-05-08  6:56     ` bug#41134: " Pierre Neidhardt
2020-05-11 11:46     ` [bug#41134] " Nicolò Balzarotti
2020-05-11 12:14       ` Pierre Neidhardt
2020-05-11 14:18         ` Raghav Gururajan [this message]
2020-05-11 15:07           ` Nicolò Balzarotti
2020-05-11 15:10             ` Raghav Gururajan
2020-05-14 17:14               ` Pierre Neidhardt
2020-05-11 11:38 ` [bug#41134] LibAppIndicator Raghav Gururajan

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=3d720723-7dac-1ab1-0c04-d9b7818a6511@disroot.org \
    --to=raghavgururajan@disroot.org \
    --cc=41134@debbugs.gnu.org \
    --cc=anothersms@gmail.com \
    --cc=mail@ambrevar.xyz \
    /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.