Re: [PATCH 2/5] diff --quiet
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Mar 15, 2007, 10:37 UTC
- Message-ID
- <Pine.LNX.4.63.0703151136470.22628@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <81b0412b0703150119l705eefb6h6af44b9452db83e2@mail.gmail.com>
Hi,
On Thu, 15 Mar 2007, Alex Riesen wrote:
Show 21 quoted lines
> On 3/15/07, Junio C Hamano <junkio@cox.net> wrote:
> > > Now I'm happy :)
> > >
> > > ~/linux$ time git diff-tree -r -s v2.6.16 v2.6.20
> > >
> > > real 0m0.137s
> > > user 0m0.117s
> > > sys 0m0.020s
> > > ~/linux$ time ~/projects/git-diff/git-diff-tree -r --quiet v2.6.16
> > v2.6.20
> > >
> > > real 0m0.006s
> > > user 0m0.000s
> > > sys 0m0.007s
> >
> > You do not need diff-tree --quiet to do that!
> >
> > $ git-rev-parse v2.6.16^{tree} v2.6.20^{tree}
> >
>
> Why would I want to benchmark --quiet with rev-parse?It is not benchmarking, but it is a faster solution: you can see if two trees are different by comparing their SHA-1s.
(That, however, works only if you do not want something like "git diff -w"...)
Ciao, Dscho