| commit | 2f82f760e1b2630073a05c44fe70bdce9706d9e5 | |
| author | Linus Torvalds <torvalds@linux-foundation.org> | |
| Sat, 18 Aug 2007 22:52:55 +0000 (18 15:52 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sun, 19 Aug 2007 18:45:31 +0000 (19 11:45 -0700) | ||
| tree | 708453d64796eb617cb8a1602959e00356693315 | treesnapshot (tar.gz zip) |
| parent | 1211be6bed1146dcef953c7c2ab332ee995f7152 | commitdiff |
Take binary diffs into account for "git rebase"
We used to not generate a patch ID for binary diffs, but that means that
some commits may be skipped as being identical to already-applied diffs
when doing a rebase.
So just delete the code that skips the binary diff. At the very least,
we'd want the filenames to be part of the patch ID, but we might also want
to generate some hash for the binary diff itself too.
This fixes an issue noticed by Torgil Svensson.
Tested-by: Torgil Svensson <torgil.svensson@gmail.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
We used to not generate a patch ID for binary diffs, but that means that
some commits may be skipped as being identical to already-applied diffs
when doing a rebase.
So just delete the code that skips the binary diff. At the very least,
we'd want the filenames to be part of the patch ID, but we might also want
to generate some hash for the binary diff itself too.
This fixes an issue noticed by Torgil Svensson.
Tested-by: Torgil Svensson <torgil.svensson@gmail.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| diff.c | diffblobblamehistory |