unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 51103-done@debbugs.gnu.org
Subject: bug#51103: [PATCH core-updates-frozen] news: Notify of Wayland support in GDM
Date: Mon, 15 Nov 2021 11:50:37 +0100	[thread overview]
Message-ID: <87ilwt7kw2.fsf@gnu.org> (raw)
In-Reply-To: <OhFe4Xib1yIsyuLJLA-lS7rt7BFym9U0j4w0yWWSfDokg1y88veTccmxHzirsu2tepVFbYau5kY52M4v-do_bSG0TF-zaEQ8-20FxhxzMbY=@jpoiret.xyz> (Josselin Poiret's message of "Fri, 08 Oct 2021 21:36:13 +0000")

Hello,

Josselin Poiret <dev@jpoiret.xyz> skribis:

> I've written a news entry to inform users of the newly added Wayland support in GDM.
> After discussing it in issue 50563, we thought it'd also be a good idea to switch Wayland mode on by default, but I don't know when it would be best to do so.
> This news entry contains a warning about that change as well. Also, I've written a warning mechanism (not included here) for people using the default value, which I could also add if needed, before or after the change.

Sure, you can always send it separately.

> As a side-note, I've put the current commit id, but it'll need to be changed when merging. I don't if there's something/someone that keeps track of everything that needs to be done when merging, so I'm just writing this here.

That’s a good idea.

>>From a8ebc5fca116900b1fba3b21af418f87e0655ce4 Mon Sep 17 00:00:00 2001
> From: Josselin Poiret <dev@jpoiret.xyz>
> Date: Fri, 8 Oct 2021 23:14:51 +0200
> Subject: [PATCH] news: Notify of Wayland support in GDM
>
> * etc/news.scm: Add a news entry.

Applied, and apologies for the delay!

Ludo’.




      reply	other threads:[~2021-11-15 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 21:36 [bug#51103] [PATCH core-updates-frozen] news: Notify of Wayland support in GDM Josselin Poiret
2021-11-15 10:50 ` Ludovic Courtès [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=87ilwt7kw2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=51103-done@debbugs.gnu.org \
    --cc=dev@jpoiret.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 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).