| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
The old (2.1) GNU patch has outlived its days. The major
local changes have been moved into the less restrictedly
licensed patch(1) we adopted in usr.bin/ .
A much newer version of GNU patch is available in the
ports tree (devel/patch).
Disconnect from the build and remove.
|
|
|
|
|
|
|
|
| |
to a dynamically allocated one in order to support input lines of
arbitrary length.
Approved by: kan (mentor)
MFC after: 1 month
|
|
|
|
|
|
|
| |
buffer-safe string functions. The rest of the code is still probably
unsafe.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
our patch to look a little more like NetBSD's, and has the nice characteristic
that the object code is exactly the same after the change as before it (even in
patch.c and pch.c, which have pesky 'assert' statements in them).
Reviewed by: /sbin/md5 on i386, alpha, sparc64
MFC after: 3 days
|
|
|
|
|
|
|
| |
patch file on command line instead of stdin.
Submitted by: Joseph Mallett <jmallett@xMach.org>
MFC after: 1 month
|
|
|
|
|
|
| |
a patch, returning -f/--force and -t/--batch to their previous semantics.
Pointed out by: asami
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, using -S/--skip, -f/--force, or -t/--batch to skip a patch in
a patchset still registers a failure which causes patch to return a
non-zero exit code. This is particularly undesirable with regards to
ports as there is no way to ignore the non-zero code. (Luckily, we don't
currently have any ports that make use of any of these options.)
The PR (yes, my own) is slightly incorrect: It states that -f does indeed
properly skip patches. It does, but it still sets the failure flag causing
patch to return non-zero.
PR: 19638
Submitted by: kbyanc@posi.net
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
as it was in hacked FreeBSD version
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
also remove -Wall that I acidentally committed last time I was here...
Submitted-by: Philippe Charnier
Closes PR#2998
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
controlling terminal is closed. Now the function ask() will return 1 when th
input is known to come from a file or terminal, or it will return 0 when ther
was a read error.
Modified the question "Skip patch?" so that on an error from ask it will skip
the patch instead of looping.
Closes PR#777
2.2 candidate
|
| |
|
|
|
|
| |
Reviewed by: phk
|
| |
|
|
|
|
| |
ports, until I saw the the commit messages, that is! :-) All changed backed out.
|
|
|
|
| |
a patch before actually applying it.
|
|
|