[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Transport links between bookmark files... Here's the code
From: |
pg |
Subject: |
Re: lynx-dev Transport links between bookmark files... Here's the code |
Date: |
Mon, 5 Jul 1999 09:14:40 -0600 (MDT) |
In a recent note, Kim DeVaughn said:
> Date: Mon, 5 Jul 1999 00:58:39 -0600
>
> please use "unified" (or at least "context") diffs. And let diff do
> the work of matching original and updated files.
>
> Setup two dirs with the lynx distribution in each, named something like
> lynx2.8.3dev.3.orig and lynx2.8.3dev.3.work.
>
TD graciously added a makefile target I requested, "lynx.patch" which I
suggested to generate patches. Mentioned in README. This presumes
the directory structure
________________
| |
| Anything |
|______________|
| |
__________V__ ___V_________
| | | |
| orig | | lynx2-8-3 |
|___________| |___________|
|
______V______
| |
| lynx2-8-3 |
|___________|
I used "diff -c" rather than "diff -u" because "-u" isn't POSIX.
> Make all your changes within the *.work dir, and when you're satisfied
(in this case, the source tree on the right)
> with the changes, do a "make distclean" in *.work, and check for any
(the "lynx.patch) target includes some distcleans in the "orig"
source tree.)
> and check that no extraneous files have been picked up in the process
> with something like:
>
> grep +++ patch
>
> which should give you a list of the changed/added files that you expect.
>
The "lynx.patch" target includes a similar filter.
-- gil
lynx-dev Re: Transport links between bookmark files... Here's the code, Michael Warner, 1999/07/06