Re: git-format-patch for binary files / merges [Re: Expose subprojects as special files to "git diff" machinery]
- From
Junio C Hamano <junkio@cox.net>
- Date
- Apr 18, 2007, 16:08 UTC
- Message-ID
- <7vlkgpis2m.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <alpine.LFD.0.98.0704180831330.2828@woody.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> writes:
Show 5 quoted lines
> We do already support binary patches, so those can be represented well in > a patch (but you need "git-apply" to apply them, so they are disabled by > default.. And while we have tests for them, I suspect not a lot of people > really use them widely, so who knows how complete the coverage is. For > example, will "git rebase" really work? Probably. Do I know for sure? No).
I've seen it in action for at least a few times in my day-job, so it appears to work ;-)
Show 5 quoted lines
> I used "bundles" once or twice under BK (it was called "bk send" and > "bk receive + bk resolve" or something like that), and I hated them. It > wasn't BK's fault: I just found the workflow annoying. So I haven't > even tested the git bundles, but if what you were looking for was to do > a "git push/pull" by email, they are what you'd be using.
I've send a bundle over e-mail exactly once; it appears to work, too.