From: Junio C Hamano <junkio@cox.net>
To: Marco Costalba <mcostalba@yahoo.it>
Cc: git@vger.kernel.org
Subject: Re: Check for differents trees
Date: Tue, 08 Nov 2005 09:13:55 -0800 [thread overview]
Message-ID: <7vhdanhxkc.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051106190249.39384.qmail@web26314.mail.ukl.yahoo.com> (Marco Costalba's message of "Sun, 6 Nov 2005 11:02:49 -0800 (PST)")
Marco Costalba <mcostalba@yahoo.it> writes:
> as you said, the speed is almost the same but your way is clearly better.
How often do you do this --diff-filter=AD and why?
If it is a common enough operation, we could add a specific hack
to stop feeding the diff machinery with unwanted kind of changes
when diff-filter is set and none of -B/-C/-M are used. That
_might_ speed things up for you.
next prev parent reply other threads:[~2005-11-08 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 19:02 Check for differents trees Marco Costalba
2005-11-08 17:13 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-10 6:57 Marco Costalba
2005-11-10 6:35 Marco Costalba
2005-11-06 15:38 Marco Costalba
2005-11-06 18:09 ` Junio C Hamano
2005-11-06 18:24 ` 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=7vhdanhxkc.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=mcostalba@yahoo.it \
/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