all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 28404@debbugs.gnu.org
Subject: [bug#28404] The complete Google Noto Fonts
Date: Mon, 17 Jan 2022 14:16:39 +0100	[thread overview]
Message-ID: <87k0eypknc.fsf@gnu.org> (raw)
In-Reply-To: <86y23jirs4.fsf_-_@gmail.com> (zimoun's message of "Thu, 13 Jan 2022 16:23:07 +0100")

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> The primary author is not responding since years.  What do we do for the
> patch series?  On one hand, piece of work had already been done and on
> the other hand, other piece of work is still missing.
>
> Is someone interested in helping to clean the work already done for
> easing the merge?

I think in this case it’s okay to close as “donewontfix” or something
along these lines.

The patch is still around and anyone interested in it can pick it up
from the archive.  Clearly, leaving issues open forever makes it harder
for us all to see where our attention is needed, so closing after a long
period of inactivity sounds like the right course of action to me.

Thanks,
Ludo’.




  reply	other threads:[~2022-01-17 14:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-10  9:06 [bug#28404] The complete Google Noto Fonts ng0
2017-09-11  8:27 ` Ludovic Courtès
2017-09-11 10:57   ` ng0
2017-09-11 11:55     ` Ludovic Courtès
2017-09-11 12:21     ` ng0
2017-09-12 12:51       ` Ludovic Courtès
2017-09-12 14:51         ` ng0
2017-09-12 15:22           ` Ludovic Courtès
2017-09-25 12:25             ` ng0
2022-01-13 15:23               ` zimoun
2022-01-17 13:16                 ` Ludovic Courtès [this message]
2022-01-17 14:23                   ` zimoun
2022-01-17 16:07                     ` Ludovic Courtès

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=87k0eypknc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=28404@debbugs.gnu.org \
    --cc=zimon.toutoune@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.