From: Junio C Hamano <gitster@pobox•com>
To: Catalin Marinas <catalin.marinas@gmail•com>
Cc: Linus Torvalds <torvalds@linux-foundation•org>,
Johannes Schindelin <Johannes.Schindelin@gmx•de>,
git <git@vger•kernel.org>
Subject: Re: [PATCH] diff -- file1 file2: do not default to --no-index inside a git repository
Date: Fri, 23 May 2008 22:17:23 -0700 [thread overview]
Message-ID: <7vfxs8p9gc.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7v8wy0r2pa.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Fri, 23 May 2008 17:00:17 -0700")
Junio C Hamano <gitster@pobox•com> writes:
> I think ripping out --no-index from git-diff-files is probably the first
> step. "git diff" also needs to fixed as Linus outlined, but that is a
> separate topic.
>
> How about doing something like this as a start? At least that would get
> well behaved Porcelains like stg unstuck?
> ...
Please do not use this one, not just yet.
The series to fix this unfortunately is turning out to be larger than I
hoped for, but the result is looking very promising ;-).
prev parent reply other threads:[~2008-05-24 5:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 14:20 git diff-files weirdness (bug?) Catalin Marinas
2008-05-23 16:14 ` Linus Torvalds
2008-05-23 16:50 ` Linus Torvalds
[not found] ` <7vbq2wsxnk.fsf@gitster.siamese.dyndns.org>
2008-05-23 22:49 ` [PATCH] diff -- file1 file2: do not default to --no-index inside a git repository Johannes Schindelin
2008-05-23 22:50 ` [ALTERNATIVE PATCH] diff " Johannes Schindelin
2008-05-24 7:25 ` Junio C Hamano
2008-05-24 7:25 ` [PATCH 1/3] tests: do not use implicit "git diff --no-index" Junio C Hamano
2008-05-24 7:26 ` [PATCH 2/3] diff-files: do not play --no-index games Junio C Hamano
2008-05-24 7:26 ` [PATCH 3/3] "git diff": do not ignore index without --no-index Junio C Hamano
2008-05-24 0:00 ` [PATCH] diff -- file1 file2: do not default to --no-index inside a git repository Junio C Hamano
2008-05-24 5:17 ` Junio C Hamano [this message]
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=7vfxs8p9gc.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=catalin.marinas@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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