From: Will Senn <will.senn@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Traditional method of dealing with embedded shar files
Date: Mon, 20 Jul 2020 13:11:11 -0500 [thread overview]
Message-ID: <a24ba1d6-c4f9-0e6b-0841-c9b087e4560b@gmail.com> (raw)
In-Reply-To: <CANCZdfouoVidk9q2vhXVcGM3ha5ZkK0_2smxLwQ8C_KTGR8nsQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
On 7/20/20 12:55 PM, Warner Losh wrote:
> Will said:
>
> My questions for y'all are how would you go about doing this? Use
> vi to delete everything through the ==== cut here line? Use some
> combination of standard unix tools to chop it up? What was your
> workflow for patching up the system using these files?
>
>
> sed -e '1,/---cut here---/d' < $patch | sh -x
>
> is what I use, but there's a wide variety of 'cut here' lines in the
> 2.11BSD patches, so I have had to taylor to each patch.
Thanks, this is nice and simple. I'll be on the lookout for the differences.
Will
[-- Attachment #2: Type: text/html, Size: 1615 bytes --]
next prev parent reply other threads:[~2020-07-20 18:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 17:23 Will Senn
2020-07-20 17:44 ` Clem Cole
2020-07-20 17:52 ` Clem Cole
2020-07-20 17:56 ` Warner Losh
2020-07-20 18:08 ` Richard Salz
2020-07-20 18:07 ` Will Senn
2020-07-24 18:29 ` Random832
2020-07-24 18:46 ` Will Senn
2020-07-24 18:57 ` Clem Cole
2020-07-24 19:21 ` Will Senn
2020-07-25 2:00 ` Dave Horsfall
2020-07-20 17:55 ` Warner Losh
2020-07-20 18:11 ` Will Senn [this message]
2020-07-20 18:41 ` Clem Cole
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=a24ba1d6-c4f9-0e6b-0841-c9b087e4560b@gmail.com \
--to=will.senn@gmail.com \
--cc=imp@bsdimp.com \
--cc=tuhs@minnie.tuhs.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).