From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Raghav Gururajan <rvgn@disroot.org>
Cc: 35586@debbugs.gnu.org
Subject: bug#35586: GNOME
Date: Sun, 5 May 2019 22:50:14 +0200 [thread overview]
Message-ID: <20190505205014.rlasyz64r44viqyh@pelzflorian.localdomain> (raw)
In-Reply-To: <20190505193653.9B62A30856@disroot.org>
On Sun, May 05, 2019 at 03:36:51PM -0400, Raghav Gururajan wrote:
> Florian! The link you provided is awesome.
>
> I strongly request the devs to use that link (https://blogs.gnome.org/mcatanzaro/2016/09/21/gnome-3-22-core-apps/) to fix this bug.
There actually also is:
https://blogs.gnome.org/mcatanzaro/2017/08/13/gnome-3-26-core-applications/
This is less detailed than the link before, but it is more recent. I
do not remember reading a more recent post on GNOME core applications
on Planet GNOME, but I may have forgotten.
Regards,
Florian
next prev parent reply other threads:[~2019-05-05 20:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 18:20 bug#35586: GNOME Raghav Gururajan
2019-05-05 18:52 ` pelzflorian (Florian Pelz)
2019-05-05 19:23 ` Raghav Gururajan
2019-05-05 20:48 ` pelzflorian (Florian Pelz)
2019-05-05 19:36 ` Raghav Gururajan
2019-05-05 20:50 ` pelzflorian (Florian Pelz) [this message]
2019-05-06 7:51 ` Raghav Gururajan
2019-05-06 9:05 ` pelzflorian (Florian Pelz)
2019-05-06 14:02 ` Raghav Gururajan
2019-05-06 7:57 ` Raghav Gururajan
2019-05-06 9:14 ` pelzflorian (Florian Pelz)
2019-05-06 14:05 ` Raghav Gururajan
2019-05-06 19:20 ` Tobias Geerinckx-Rice
2019-05-06 19:30 ` Raghav Gururajan
2019-05-07 6:29 ` Raghav Gururajan
2019-05-11 9:48 ` Raghav Gururajan
2019-05-11 10:08 ` Ricardo Wurmus
2019-05-11 10:30 ` Raghav Gururajan
2019-07-02 22:44 ` bug#35586: Raghav Gururajan
2019-07-02 23:21 ` bug#35586: SUMMARY (Re-Write) Raghav Gururajan
2019-11-13 5:44 ` bug#35586: GNOME Core Applications Raghav Gururajan
2022-05-25 6:54 ` Roman Riabenko
2022-05-25 11:08 ` Maxime Devos
2022-05-25 17:54 ` Roman Riabenko
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=20190505205014.rlasyz64r44viqyh@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=35586@debbugs.gnu.org \
--cc=rvgn@disroot.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).