Github messages for voidlinux
 help / color / mirror / Atom feed
From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] GNOME 42
Date: Thu, 24 Mar 2022 02:02:13 +0100	[thread overview]
Message-ID: <20220324010213.TiN-hh3g5uTF2gtKGVk9pKoogsJTBQjwKeuywpAn8b4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36310@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 249 bytes --]

New comment by abenson on void-packages repository

https://github.com/void-linux/void-packages/pull/36310#issuecomment-1076965188

Comment:
Don't open and close PRs.  Force push to the branch to rewrite it.  Opening and closing just creates noise.

  parent reply	other threads:[~2022-03-24  1:02 UTC|newest]

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24  0:59 [PR PATCH] " oreo639
2022-03-24  1:00 ` [PR PATCH] [Closed]: " oreo639
2022-03-24  1:02 ` abenson [this message]
2022-03-24  1:01 [PR PATCH] " oreo639
2022-03-24  1:02 ` abenson
2022-03-24  1:02 ` oreo639
2022-03-24  1:07 ` classabbyamp
2022-03-24  1:08 ` oreo639
2022-03-24 20:15 ` oreo639
2022-03-24 21:48 ` paper42
2022-03-26 16:28 ` paper42
2022-03-26 16:35 ` paper42
2022-03-26 17:57 ` oreo639
2022-03-26 17:57 ` oreo639
2022-03-27 20:38 ` paper42
2022-03-27 20:44 ` oreo639
2022-03-31 18:32 ` paper42
2022-03-31 18:33 ` paper42
2022-04-02 16:20 ` oreo639
2022-04-02 16:57 ` oreo639
2022-04-02 17:16 ` oreo639
2022-04-02 17:34 ` oreo639
2022-04-02 17:45 ` oreo639
2022-04-07 11:41 ` paper42
2022-04-07 16:03 ` oreo639
2022-04-07 16:56 ` paper42
2022-04-07 17:14 ` oreo639
2022-04-09 11:00 ` paper42
2022-04-11  8:04 ` oreo639
2022-04-11  8:54 ` oreo639
2022-04-15 19:21 ` paper42
2022-04-15 19:40 ` paper42
2022-04-15 19:49 ` paper42
2022-04-15 21:23 ` oreo639
2022-04-15 21:32 ` oreo639
2022-04-15 22:13 ` oreo639
2022-04-15 22:13 ` oreo639
2022-04-15 22:14 ` oreo639
2022-04-15 22:16 ` oreo639
2022-04-15 22:32 ` oreo639
2022-04-15 23:22 ` oreo639
2022-04-15 23:25 ` oreo639
2022-04-16 17:41 ` paper42
2022-04-17  2:25 ` oreo639
2022-04-17  2:25 ` oreo639
2022-04-17  4:16 ` q66
2022-05-01 20:31 ` oreo639
2022-05-01 20:31 ` oreo639
2022-05-01 20:46 ` paper42
2022-05-01 20:46 ` paper42
2022-05-01 21:13 ` oreo639
2022-05-01 21:14 ` oreo639
2022-05-01 21:14 ` oreo639
2022-05-01 21:14 ` oreo639
2022-05-01 21:16 ` oreo639
2022-05-01 21:18 ` oreo639
2022-05-01 21:23 ` oreo639
2022-05-01 21:26 ` oreo639
2022-05-02  2:02 ` oreo639
2022-05-02  2:03 ` oreo639
2022-05-02  4:30 ` oreo639
2022-05-09  2:25 ` oreo639
2022-05-09 21:25 ` paper42
2022-05-09 22:42 ` q66
2022-05-09 23:34 ` oreo639
2022-06-01 20:23 ` mdkcore0
2022-06-01 20:47 ` oreo639
2022-06-01 20:48 ` oreo639
2022-06-01 20:49 ` oreo639
2022-06-01 20:49 ` oreo639
2022-06-01 20:53 ` oreo639
2022-06-01 20:59 ` oreo639
2022-06-01 21:02 ` oreo639
2022-06-02  3:20 ` oreo639
2022-06-02 14:11 ` mdkcore0
2022-06-08 17:41 ` paper42
2022-06-08 19:14 ` oreo639
2022-06-10 22:43 ` z-ffqq
2022-06-10 22:43 ` z-ffqq
2022-06-10 22:43 ` z-ffqq
2022-06-10 22:47 ` z-ffqq
2022-06-10 22:49 ` z-ffqq
2022-06-11 17:37 ` oreo639
2022-06-11 17:50 ` paper42
2022-06-11 17:52 ` oreo639
2022-06-11 18:55 ` oreo639
2022-06-19 21:40 ` JamiKettunen
2022-06-19 21:43 ` JamiKettunen
2022-06-19 21:44 ` JamiKettunen
2022-06-19 21:45 ` JamiKettunen
2022-07-05 11:44 ` paper42
2022-07-07  2:32 ` subnut
2022-07-07  2:45 ` oreo639
2022-07-07  2:48 ` oreo639
2022-07-07  2:53 ` subnut
2022-07-07  8:07 ` brxken128
2022-07-07  8:16 ` paper42
2022-07-07  8:23 ` brxken128
2022-07-07  8:27 ` paper42
2022-07-07  8:29 ` brxken128
2022-07-07  8:32 ` paper42
2022-07-07  8:34 ` paper42
2022-07-07  8:43 ` brxken128
2022-07-07  8:46 ` paper42
2022-07-07 15:21 ` brxken128

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=20220324010213.TiN-hh3g5uTF2gtKGVk9pKoogsJTBQjwKeuywpAn8b4@z \
    --to=abenson@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).