From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: git diff: support "-U" and "--unified" options properly
Date: Sat, 13 May 2006 14:22:41 -0700 [thread overview]
Message-ID: <7vpsihsjq6.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0605131404391.3866@g5.osdl.org> (Linus Torvalds's message of "Sat, 13 May 2006 14:05:33 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> On Sat, 13 May 2006, Junio C Hamano wrote:
>>
>> Linus Torvalds <torvalds@osdl.org> writes:
>>
>> > [ Maybe this can still hit 1.3.3? ]
>>
>> Ah, we did not pass the diffopt to the function builtin_diff() in
>> 1.3.X series, so not really.
>
> Ahh, ok. Never mind. It's not like people have been clamoring for it, it
> just seemed to be such a _silly_ thing.
>
> Might as well just go into the curren development tree, and then we'll
> have it fixed eventually (1.4.0?)
No question about that part. I've been meaning to start drawing
the line of what to have in 1.4 and what to leave out, but the
last week was shot so I haven't got around to.
A rough outline.
I'd like to have the following topics from "next":
* cvsserver and cvsexportcommit updates (ml/cvs)
Ready.
* config syntax (lt/config)
Ready.
* built-in grep (jc/grep)
Ready.
* built-in format-patch (js/fmt-patch)
Some features are still missing compared to the script
version.
* remotes/ information from .git/config (js/fetchconfig)
This by itself is more or less ready, but I would like to
further adjust it to the "per branch configuration"
discussion before pushing it out.
I'd like to eventually arrange things like this.
[branch "master"]
remote = "ko-private"
; prevent "reset --hard" from rewinding past this.
rewind-barrier = refs/heads/ko-master
; my private build areas on the kernel.org machines
[remote "ko-private"]
url = "x86-64-build.kernel.org:git"
url = "i386-build.kernel.org:git"
push = master:origin
push = next:next
push = +pu:pu
push = maint:maint
; for publishing and keeping track of what I pushed there last time
[remote "ko"]
url = "kernel.org:/pub/scm/git/git.git"
push = master:master
push = next:next
push = +pu:pu
push = maint:maint
fetch = master:ko-master
fetch = next:ko-next
fetch = +pu:ko-pu
fetch = maint:ko-maint
next prev parent reply other threads:[~2006-05-13 21:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 20:23 git diff: support "-U" and "--unified" options properly Linus Torvalds
2006-05-13 20:30 ` Junio C Hamano
2006-05-13 20:59 ` Junio C Hamano
2006-05-13 21:05 ` Linus Torvalds
2006-05-13 21:22 ` Junio C Hamano [this message]
2006-05-13 22:39 ` Linus Torvalds
2006-05-15 0:39 ` Junio C Hamano
2006-05-15 0:58 ` Linus Torvalds
2006-05-15 1:51 ` Junio C Hamano
2006-05-15 3:49 ` Linus Torvalds
2006-05-14 7:00 ` Martin Langhoff
2006-05-14 12:57 ` Josef Weidendorfer
2006-05-14 17:36 ` Junio C Hamano
2006-05-14 20:49 ` Branch relationships (was:Re: git diff: support "-U" and "--unified" options properly) Josef Weidendorfer
2006-05-14 21:20 ` Branch relationships Junio C Hamano
2006-05-14 22:01 ` Josef Weidendorfer
2006-05-14 22:19 ` Junio C Hamano
2006-05-14 23:04 ` Josef Weidendorfer
2006-05-14 23:55 ` Junio C Hamano
2006-05-15 1:48 ` Josef Weidendorfer
2006-05-15 2:11 ` 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=7vpsihsjq6.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).