Re: git-format-patch for binary files / merges [Re: Expose subprojects as special files to "git diff" machinery]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/18/07, Sam Vilain <sam@xxxxxxxxxx> wrote:
Linus Torvalds wrote:
>> Isn't this dangerous because it looks just like a normal diff with a
>> file being rewritten, when in truth it is a tree entry record being
>> rewritten.
>>
> Well, that's exactly what symlinks do too.
>
> You have to look at the mode to know what the rewriting *means*.
>
> But yeah, I wouldn't object at all to making it an "extended git header"
> instead (possibly just for subprojects, possibly for symlinks too)
>

Speaking of 'custom' patch file formats, anyone put any thought to a
format for the commits which can't be represented with patch, like
binary files and merges?


There is binary diff (look for --binary in Documentation/).
And regarding merges: have you looked at git-bundle yet?
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]