From: Junio C Hamano <junkio@cox.net>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Jochen Roemling <jochen@roemling.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: change of git-diff-tree and symlinks
Date: Sun, 29 May 2005 11:55:57 -0700 [thread overview]
Message-ID: <7vwtphn9oi.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050529150656.GA27127@vrfy.org> (Kay Sievers's message of "Sun, 29 May 2005 17:06:56 +0200")
>>>>> "KS" == Kay Sievers <kay.sievers@vrfy.org> writes:
>> Also there is a new parameter '-p' that allows the output of a patch
>> directly instead of creating it with the help of temporary files as you
>> do it in gitweb.
KS> Sure, gitweb did the diffs before git was able to do that. And it does
KS> not really matter who is creating the temp-files, the cgi or the
KS> git-binaries. :)
I agree that you are doing the right thing here. In a scripted
environment it usually is more sensible not to use '-p' unless
generating the diff is the _only_ thing you are doing. '-p' is
primarily for people who ends up using the bare plumbing
interactively.
KS> If things are stable some day, I may switch that over and maybe even
KS> support the nice rename detection.
Sorry for being the primary culprit for the disruption ;-).
You do not have to use '-p' to be able to use rename detection
nor any other diffcore stuff. If you are processing
"git-diff-tree -r" output right now, you can already process
"git-diff-tree -r -B -M -S'foo' -Oorder" output just fine and
leave your downstream processing the same as is.
next prev parent reply other threads:[~2005-05-29 18:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 11:17 change of git-diff-tree and symlinks Kay Sievers
2005-05-25 18:08 ` Linus Torvalds
2005-05-25 18:35 ` Kay Sievers
2005-05-25 19:40 ` Junio C Hamano
2005-05-25 22:06 ` [PATCH] Adjust show-files test for dotfiles Junio C Hamano
2005-05-25 22:07 ` [PATCH] Fix type-change handling when assigning the status code to filepairs Junio C Hamano
2005-05-25 22:26 ` change of git-diff-tree and symlinks Kay Sievers
2005-05-25 22:43 ` Junio C Hamano
2005-05-25 22:47 ` Linus Torvalds
2005-05-25 23:00 ` [PATCH] Mode only changes from diff Junio C Hamano
2005-05-26 2:11 ` [PATCH] Test case portability fix Junio C Hamano
2005-05-26 2:36 ` Linus Torvalds
2005-05-26 2:55 ` Junio C Hamano
2005-05-29 14:16 ` change of git-diff-tree and symlinks Jochen Roemling
2005-05-29 15:06 ` Kay Sievers
2005-05-29 16:06 ` Jochen Roemling
2005-05-29 16:14 ` Sebastian Kuzminsky
2005-05-30 3:17 ` Sebastian Kuzminsky
2005-05-29 18:55 ` Junio C Hamano [this message]
2005-05-29 21:32 ` Petr Baudis
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=7vwtphn9oi.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jochen@roemling.net \
--cc=kay.sievers@vrfy.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.