From: Jody Bruchon <jody@jodybruchon.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Any reason not to add elksnet + elkscmd?
Date: Thu, 05 Mar 2015 09:57:01 -0500 [thread overview]
Message-ID: <54F86EBD.5070102@jodybruchon.com> (raw)
Unless anyone on the list has objections, I'm planning to merge elksnet
and elkscmd. It seems silly to have all the other command-line tools in
elkscmd (including many ELKS-specific versions of programs) but then
have a tiny number of programs in a totally separate directory tree that
only serves to make the build system more needlessly complex than it
already is.
If the spirit of the original division was to keep them separated from
ports of "normal" programs, I could push them to a new directory
"elkscmd/elksnet" but it seems like "elkscmd/inet" would be just as good.
Any thoughts/preferences?
-Jody
reply other threads:[~2015-03-05 14:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54F86EBD.5070102@jodybruchon.com \
--to=jody@jodybruchon.com \
--cc=linux-8086@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).