Re: stgit truncates binary files to zero length when applying patches
- From
Junio C Hamano <junkio@cox.net>
- Date
- Nov 16, 2005, 18:30 UTC
- Message-ID
- <7vr79g8mys.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <b0943d9e0511160311k725526d8v@mail.gmail.com>
Catalin Marinas <catalin.marinas@gmail.com> writes:
> ... When pushing a patch, if > a merge is needed (like in your case, the base of the foo patch has > changed), StGIT first tries "git-diff-tree | git-apply" for speed > reasons. If this fails, it falls back to a three-way merge.
I think many of the scripts rely on git-apply failing reliably for unapplicable patches. I'll do a new test script in git.git/t and if it fails on binary files, try to fix it today.
Incidentally, for the last couple of days, I was working on adding a very limited binary file diff support to "diff piped to apply" pattern, and the result has been posted as "reworked rebase" patches. It is very limited in the sense that the diff output does not attempt to be useful if the patch consumer does not have both pre- and post-image blob, but for the use of StGIT's internal patch replaying purposes that is not a concern, so you might be interested in taking a look.