From: Junio C Hamano <junkio@cox.net>
To: GIT <git@vger.kernel.org>
Subject: Re: git-diff-files -z output
Date: Sun, 22 May 2005 10:17:40 -0700 [thread overview]
Message-ID: <7v3bsffadn.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050522170540.GO15178@cip.informatik.uni-erlangen.de> (Thomas Glanzmann's message of "Sun, 22 May 2005 19:05:40 +0200")
>>>>> "TG" == Thomas Glanzmann <sithglan@stud.uni-erlangen.de> writes:
TG> I am adopting to the new format.
TG> Are the fields supposed to be seperated by space or tab?
Please see Documentation/diff-format.txt; find the below in the
archive for the full description of why we wanted this format
update.
From: Junio C Hamano <junkio@cox.net>
Subject: Re: updated design for the diff-raw format.
To: git@vger.kernel.org
Date: Sat, 21 May 2005 16:17:33 -0700
(second of the replayed message, with blessing from Linus)
Date: Sat, 21 May 2005 11:24:31 -0700 (PDT)
From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH 3/3] Diff overhaul, adding the other half of copy detection.
Message-ID: <Pine.LNX.4.58.0505211107160.2206@ppc970.osdl.org>
On Sat, 21 May 2005, Junio C Hamano wrote:
>
> Once we start to think of it this way, it becomes quite tempting
> to change the diff-raw format to actually match the above
> concept.
I agree, and I was going to suggest changing the "raw" diff output for all
the same reasons. So I think you should do it, as the old format was based
on not really knowing where this all would take us. I think your proposed
format is visually nicer, and it's obviously more flexible.
next prev parent reply other threads:[~2005-05-22 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 17:05 git-diff-files -z output Thomas Glanzmann
2005-05-22 17:17 ` Junio C Hamano [this message]
2005-05-22 17:27 ` Thomas Glanzmann
2005-05-22 17:32 ` Thomas Glanzmann
2005-05-22 17:38 ` Thomas Glanzmann
2005-05-22 17:49 ` Junio C Hamano
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=7v3bsffadn.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).