From: mmnmnnmnmm <mmnmnnmnmm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: nawk: update to 20200702
Date: Sat, 18 Jul 2020 13:35:26 +0200 [thread overview]
Message-ID: <20200718113526.9xAgf98GxUnw-a5EdxKqlCfbbhCwzPx6By1LHdW99KQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23621@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
New comment by mmnmnnmnmm on void-packages repository
https://github.com/void-linux/void-packages/pull/23621#issuecomment-660469955
Comment:
> I don't think its that widely used piece of software.
We all have different interpretations of "widely" :). I meant rather, it is used as the implementation of awk in the *BSDs and is the reference awk, which makes it quite useful for testing portable awk scripts.
I also forgot to make clear that the last "release" of nawk was just a singular tagged commit. They have never done releases; you can see in the git history of this file that the template previously used arbitrary commits before that "release".
plan9port is in the same situation where upstream doesn't make releases for similar reasons but new versions from git commits still get merged by some of the maintainers, so I don't know how the Void team wants to handle this.
next prev parent reply other threads:[~2020-07-18 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 18:25 [PR PATCH] " mmnmnnmnmm
2020-07-17 19:14 ` Chocimier
2020-07-17 19:47 ` mmnmnnmnmm
2020-07-18 6:38 ` fosslinux
2020-07-18 7:06 ` flexibeast
2020-07-18 7:10 ` fosslinux
2020-07-18 11:35 ` mmnmnnmnmm [this message]
2021-01-29 0:59 ` ericonr
2021-01-29 13:57 ` mmnmnnmnmm
2021-01-29 14:04 ` [PR PATCH] [Updated] " mmnmnnmnmm
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=20200718113526.9xAgf98GxUnw-a5EdxKqlCfbbhCwzPx6By1LHdW99KQ@z \
--to=mmnmnnmnmm@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).