Commits

Commit:
1b1b91abdb4cd380995e3542580daa8700d93f6f
From:
Omar Polo <op@omarpolo.com>
Date:
style: remove double semicolon
diff | patch | tree
Commit:
06c44edcbf03f02d1d7c07f9360de526dd4203d3
From:
Stefan Sperling <stsp@stsp.name>
Date:
check for errors from fclose() in patch_file()
diff | patch | tree
Commit:
11ce22a1a15a25df1218e6cd79c7c0ff7e951b63
From:
Omar Polo <op@omarpolo.com>
Date:
plug memory and fd leak in got patch
diff | patch | tree
Commit:
35095610b1bb11a6c722f6d42f6609bd308531a8
From:
Omar Polo <op@omarpolo.com>
Date:
got patch: use ints for line offsets instead of longs ints have the advantage that their size is more likely to be the same across the various architecture supported by OpenBSD, thus introducing less possible differences. INT_MAX is still (at least) a few order of magnitudes higher than the patches we dealt with (even abnormal ones.) suggested by stsp@
diff | patch | tree
Commit:
5b7126c502f8d046d0779dd2cb0558163c383819
From:
Omar Polo <op@omarpolo.com>
Date:
actually guarding against negative line offsets previous commit looked at some pretty zeroes returned from calloc instead of the actual numbers received.
diff | patch | tree
Commit:
2399b53d3a5f7a784efc54b86027b4f50f65ac41
From:
Omar Polo <op@omarpolo.com>
Date:
style; set datalen only once
diff | patch | tree
Commit:
71393b5c7fb0a8cff0c8fd7890c3954e3f3a9599
From:
Omar Polo <op@omarpolo.com>
Date:
got patch: guard against invalid (negative) line offsets under normal circumstances got-read-patch can't send negative line offsets; that's not an excuse not to guard the main process from those as well. This makes sure we bail out early instead of trying to apply the diff.
diff | patch | tree
Commit:
0e07a2a181ad1663e726597758495e6b8010ba97
From:
Omar Polo <op@omarpolo.com>
Date:
free patch on error
diff | patch | tree
Commit:
99b94ad7a7280ebcb23a103b28c81900bbe250ee
From:
Omar Polo <op@omarpolo.com>
Date:
got patch: ensure new and old paths are NUL-terminated
diff | patch | tree
Commit:
4bcdc8959af14bcb2e50c7f303df6c055573bc7a
From:
Omar Polo <op@omarpolo.com>
Date:
refactor got_patch / got_worktree_patch_complete let got_patch own fileindex_path and call got_worktree_patch_complete only if got_wokrtree_patch_prepare hasn't failed. suggested by stsp@
diff | patch | tree
Commit:
f2dd780737c47f6d92e6fe01cbd51bf93c91b3b3
From:
Omar Polo <op@omarpolo.com>
Date:
got patch: avoid open/sync/close the fileindex over and over again Instead of flushing the fileindex after every patch in the patchfile just reuse the same fileindex and sync it only at the end of the patch operation. This speeds up 'got patch' on large repositories by quite a lot.
diff | patch | tree
Commit:
e45f7eba7c3fe929b6bd5852f390301aeace98aa
From:
Christian Weisgerber <naddy@mips.inka.de>
Date:
got patch: switch from fseek() to fseeko(), use unary minus while here ok op
diff | patch | tree
Commit:
be33dff7fa389c620154dc06efbeae69bd002950
From:
Omar Polo <op@omarpolo.com>
Date:
got patch: fail when reading empty hunks
diff | patch | tree
Commit:
bad961bf76d36ad6f3472c7ad80f648091f56019
From:
Omar Polo <op@omarpolo.com>
Date:
got patch: allow to reverse a patch add a flag to got_patch to reverse a patch before applying and the -R flag for `got patch'. ok stsp@
diff | patch | tree
Commit:
b28327780dc2e32f03051c7d18d57db2e27e2de6
From:
Omar Polo <op@omarpolo.com>
Date:
got-read-patch: preserve all \ lines as a cheap optimization got-read-patch was sending only the "\ No newline at end of file" lines that follows an addition (a "+" line). To be able to reverse patches in the future got_patch needs to know about all of these lines instead. No functional changes intended. ok stsp@
diff | patch | tree