SecBSD/ports
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

SecBSD's official ports repository

Browse source
This commit is contained in:
purplerain 2023-08-16 22:26:55 +00:00
commit 2c0afcbbf3
Signed by: purplerain
GPG key ID: F42C07F07E2E35B7
64331 changed files with 5339189 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
devel/cvsps/patches/patch-Makefile Normal file
View file

@ -0,0 +1,12 @@
--- Makefile.orig Wed Jul 18 00:35:29 2012
+++ Makefile Wed Jul 18 00:36:54 2012
@@ -23,6 +23,9 @@ all: cvsps
cvsps: $(OBJS)
$(CC) -o cvsps $(OBJS) -lz
+.c.o:
+ $(CC) $(CFLAGS) -c -o $@ $<
+
install:
[ -d $(prefix)/bin ] || mkdir -p $(prefix)/bin
[ -d $(prefix)/share/man/man1 ] || mkdir -p $(prefix)/share/man/man1

13
devel/cvsps/patches/patch-cvsps_1 Normal file
View file

@ -0,0 +1,13 @@
--- cvsps.1.orig Wed Jul 18 00:30:20 2012
+++ cvsps.1 Wed Jul 18 00:30:31 2012
@@ -10,8 +10,8 @@ repository. A patchset in this case is defined as a s
to a collection of files, and all committed at the same time (using a
single 'cvs commit' command). This information is valuable to seeing the
big picture of the evolution of a cvs project. While cvs tracks revision
-information, it is often difficult to see what changes were committed
-'atomically' to the repository.
+information, it is often difficult to see what changes were
+committed 'atomically' to the repository.
.SH OPTIONS
.TP
.B \-h

13
devel/cvsps/patches/patch-cvsps_c Normal file
View file

@ -0,0 +1,13 @@
--- cvsps.c.orig Thu May 26 05:39:40 2005
+++ cvsps.c Wed Jul 18 00:30:09 2012
@@ -2550,9 +2550,9 @@ static void determine_branch_ancestor(PatchSet * ps, P
for (next = ps->members.next; next != &ps->members; next = next->next)
{
+ int d1, d2;
PatchSetMember * psm = list_entry(next, PatchSetMember, link);
rev = psm->pre_rev;
- int d1, d2;
/* the reason this is at all complicated has to do with a
* branch off of a branch. it is possible (and indeed