Here is some information that will serve as a gateway to your participation in the development of the nl command.
GNU coreutils
If you read this page, you will understand the whole story. Coreutils - GNU core utilities
Discussions about coreutils development are basically done on the mailing list. There are three main mailing lists. You must first subscribe to post. To subscribe, send a blank email to [email protected] with the subject line only "subscribe".
You can browse and search the archive here. coreutils Archive
This is the main mailing list where general questions and discussions are held. You can also post your request for new features here. It seems that the operation policy of this list is "If you get lost, start from this mailing list". I also throw controversial patches here. It may be an internally disliked method as it cannot be tracked by a bug tracker.
Looking at it, it is interesting that various stories are posted. For example, I sometimes see students who write their own research and ask, "I'm in trouble, but help me!" And surprisingly, you can get advice properly. However, depending on the content, you may be rigorously instructed on how to ask questions with the feeling "Let's read the source first?", So you should ask after doing what you should do properly. At least if the content contributes to the development of software, I think that there are kind people who are willing to answer.
You can browse and search the archive here. bug-coreutils Archive
This is a mailing list for working with bug trackers. This content also flows towards the coreutils list.
Release information will be sent to you on the notification mailing list.
GNU bug report logs: bugs in package coreutils
This system is only tracking and searching. Reports are posted from the bug-coreutils mailing list. Make sure to review existing reports before reporting any issues.
The official git repository is on the GNU server, but GitHub also has a mirror.
Official GNU savannah server (cgit) Official GNU savannah server (gitweb) GitHub (Mirror)
If you want to download it at hand, do the following:
$ git clone git://git.sv.gnu.org/coreutils
Basically, patches and discussions are done on the mailing list, but it seems that you can also respond by sending a pull request to GitHub.
Decoded: GNU coreutils coreutils has good development documentation. (I didn't know!) Not only the design but also how to use the GNU library is mentioned, so I think it will be very helpful when reading the source.
BusyBox
The basic flow is similar to coreutils.
Subscribe to mailing list In addition to subscribing, you can also search the archive.
Explanation of access method Official git server GitHub (Mirror)
Bug Tracking System Bugzilla.
How to post a patch
Basically, posting to the mailing list, but if you create a Morris account, you can push directly to the git server.
NetBSD
NetBSD Advent Calendar 2020, I wrote it here as an article on the 23rd day. → NetBSD nl command and Problem Reports
FreeBSD
(TBD) FreeBSD's nl has not been fully investigated, so I will add it if necessary.
Recommended Posts