On Sat, 19 Sep 2009, [email protected] wrote:
Hi,
> + external/zlib/zlib.dif
> + external/sqlite3/sqlite3.dif
> + Added .dif files for local patches to locally hosted
> 3rd party code. Pls update these when modifying original
> source locally.
> ; NOTE: I intentionally didn't add svn props to these files.
Without native EOL it will be hard to update them for none Win/DOS users
anyhow I suggest to remove them. They are redundant and such diffs can be
always generated automatically using svn diff command and for sure it's
much safer method then .diff files updated manually by developers.
If you want then you can simply add log file to store revision number just
after committing new version of given library and before appalling diff
generated for previous code. All new syncs should be done in the following
steps:
1. generate locally .diff file from last library upgrade using
svn diff -r <revision> ...
if possible check <revision> number in log file.
2. commit new library source code
3. patch new library using .diff file generated in step 1 and
update log file adding information about current revision
number
4. commit modifications
The log file is optional but it can reduce time necessary to validate exact
revision number from last library update.
best regards,
Przemek
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
