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 17:07:15 +0100	[thread overview]
Message-ID: <87fspmmjm4.fsf@gnu.org> (raw)
In-Reply-To: <86bl0afnkh.fsf@gmail.com> (zimoun's message of "Mon, 17 Jan 2022 15:23:42 +0100")

Hi,

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

> On Mon, 17 Jan 2022 at 14:16, Ludovic Courtès <ludo@gnu.org> wrote:

[...]

>> 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.
>
> The question is how to pick up.  On one hand, being still open does not
> seem to work.  On the other hand, do we document in the manual this tag
> “donewontfix” as the tag for “unfinished” patches.  For instance, some
> of these “old” patches could be good starters for people wanting to help
> but without knowing where to look at first.  WDYT?

I wouldn’t worry much.  Someone might find it via a search engine, or an
old-timer might invite them to look for it in the bug tracker.  Worst
that can happen is that someone redoes the work from scratch, which is
suboptimal but not the end of the world either.

Ludo’.




      reply	other threads:[~2022-01-17 16:14 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
2022-01-17 14:23                   ` zimoun
2022-01-17 16:07                     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fspmmjm4.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.