From: Sam Vilain <sam@vilain.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Parkins <andyparkins@gmail.com>,
git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: git-format-patch for binary files / merges [Re: Expose subprojects as special files to "git diff" machinery]
Date: Wed, 18 Apr 2007 20:46:38 +1200 [thread overview]
Message-ID: <4625DAEE.3090702@vilain.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0704151402130.5473@woody.linux-foundation.org>
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?
Sam.
next prev parent reply other threads:[~2007-04-18 8:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 18:14 Expose subprojects as special files to "git diff" machinery Linus Torvalds
2007-04-15 19:01 ` Sam Ravnborg
2007-04-15 19:05 ` Linus Torvalds
2007-04-15 19:20 ` Sam Ravnborg
2007-04-15 20:16 ` Andy Parkins
2007-04-15 21:03 ` Linus Torvalds
2007-04-18 8:46 ` Sam Vilain [this message]
2007-04-18 11:49 ` git-format-patch for binary files / merges [Re: Expose subprojects as special files to "git diff" machinery] Alex Riesen
2007-04-18 11:52 ` Johannes Schindelin
2007-04-18 15:47 ` Linus Torvalds
2007-04-18 16:08 ` Junio C Hamano
2007-04-19 8:28 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4625DAEE.3090702@vilain.net \
--to=sam@vilain.net \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.