From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] Backport cut to V7
Date: Fri, 13 Nov 2015 12:56:26 -0500 [thread overview]
Message-ID: <51DEFF94-4CE1-40BA-8BCC-5FF04A8B9EFB@ronnatalie.com> (raw)
In-Reply-To: <CADxT5N4ggDbxvbeAfwS76p4KA1vZQM3yOoeZaSQBnnqU=jWSJA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
If you’re starting with the PWB application, it’s not even a back port really. PWB was a sort of V6-ish development environment, sort of a front port.
>
> I'm not sure how old cut is, but a quick look at the code gave me the
> idea it could be backported to V7, as I'm fairly sure that cut wasn't
> in V7.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2284 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151113/49ef0dd9/attachment.bin>
prev parent reply other threads:[~2015-11-13 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 2:38 Mark Longridge
2015-11-13 17:56 ` Ronald Natalie [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=51DEFF94-4CE1-40BA-8BCC-5FF04A8B9EFB@ronnatalie.com \
--to=ron@ronnatalie.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.
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).