From: Scott Schwartz schwartz@galapagos.cse.psu.edu
Subject: diff|patch
Date: Mon, 21 Aug 1995 18:40:42 -0400 [thread overview]
Message-ID: <19950821224042.z8ojeRovoO_XeErXv3zq3Mnn6M343W9T1L9L5UGroAg@z> (raw)
I don't get it. As far as I can tell, context diffs and patch are not
a matter of unix compatability, creeping features, religious wars, or
anything like that. It's just a fact that without patch applying these
updates is intolerably arduous, and without context diffs you have to
manually examine the files, split them into sections for patch, and
copy new files into place, and suffer a greater likelihood of error.
Why do it the hard way, when simple, effective, minimalistic, software
tools are available to do the job?
next reply other threads:[~1995-08-21 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-21 22:40 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-23 2:51 diff|patch Sandy
1995-08-22 0:04 diff|patch forsyth
1995-08-21 9:08 diff|patch Vadim
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=19950821224042.z8ojeRovoO_XeErXv3zq3Mnn6M343W9T1L9L5UGroAg@z \
--to=9fans@9fans.net \
/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).