From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 74549@debbugs.gnu.org, guix-maintainers@gnu.org,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#74549] News entry for the survey
Date: Wed, 04 Dec 2024 05:55:48 +0000 [thread overview]
Message-ID: <87ldww800x.fsf@protonmail.com> (raw)
In-Reply-To: <Z0hYL5cCjm4mdcKG@3900XT>
>>> > Does it make sense to revert it (how does that end up working for
>>> > news)? I can revert with a note to keep news more directly
>>> > software-related, lest it sets a precedent. Though maybe this should
>>> > be opened up to wider discussion.
>>>
>>> I don't foresee a problem with reverting a news entry; people pulling to
>>> a commit before the reversal will see the news, those to a commit
>>> including it shouldn't see it.
>>>
>>> It's not a big deal, but in order to not set a precedent, I'd rather see
>>> it reverted. I've answered the survey, by the way!
>>
>> I think we can wait until after the deadline ends to revert it, as long
>> as it's already there.
>
> Sounds good. I'll revert by Monday, noting in the commit message why
> and as notice for what news.scm should be used for.
>
> Thanks for the understanding!
>
> John
Reverted with aa8d8d6634ccd443d7375a0bdbb120674b40178d.
Thanks for the input and understanding.
prev parent reply other threads:[~2024-12-04 5:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 20:22 [bug#74549] News entry for the survey John Kehayias via Guix-patches via
2024-11-27 6:14 ` bug#74549: " John Kehayias via Guix-patches via
2024-11-28 4:41 ` [bug#74549] " Maxim Cournoyer
2024-11-28 5:11 ` John Kehayias via Guix-patches via
2024-11-28 7:41 ` Maxim Cournoyer
2024-11-28 11:46 ` Efraim Flashner
2024-11-28 15:26 ` John Kehayias via Guix-patches via
2024-12-04 5:55 ` John Kehayias via Guix-patches via [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ldww800x.fsf@protonmail.com \
--to=guix-patches@gnu.org \
--cc=74549@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-maintainers@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=maxim.cournoyer@gmail.com \
/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.