threads / discuss / 2653

$Revision$ keyword replacement?

Subject: $Revision$ keyword replacement?

## tl;dr

4 messages between Nov 22, 2005 and Nov 22, 2005.

replies: 3people: 2as markdown or json

Santi Béjar· Nov 22, 2005, 17:36 UTC · lore
Hello:
        I'm looking for a $Revision$ replacement. I know, in git all that
        matters are the contents. So the equivalent in git could be:
        How similar this file is to the file $path in these commit(s)?
        What I use now is an ugly shell script (as you might known
        I'm not a C programer), see the attatchment.
        So I get:

311bf741d16ee5d0166639a4fafd9194e504aad3:R094 introduccio.tex sim.tex b764ee049289f5157238596cccc7a4e15f23896c:R094 introduccio.tex sim.tex f293e1ab1dfb7ff60cb269ed5b18f9222099a752:R098 introduccio.tex sim.tex f14c4b2d6799354d376e2026a5b7a85ccce48284:R098 introduccio.tex sim.tex 183af55606310218ca0e9a735dad0827acea7910:R098 introduccio.tex sim.tex 73fd2531cce3db0ca804577fb29f87f413fc4563:R096 introduccio.tex sim.tex

        Do you know any other (or better :) way to do it?
        Thanks
        Santi

#!/bin/sh ## ## find-sim finds the similarity of one file with the files in the ## selected commits ## ## The arguments are: ## $1 - file to compare ## $n n>2 - arguments for git-rev-list to select the commits ## . git-sh-setup || die "Not a git archive."

[ ! -e $1 ] && exit 1 file=$1 shift

case $GIT_DIR in
    /*)
	GIT_DIR_ORIG=$GIT_DIR;;
    *)
	GIT_DIR_ORIG=$PWD/$GIT_DIR
esac

tmp=`mktemp -t -d git-find-sim.XXXXXXX` GIT_DIR_TEMP=$tmp mkdir -p $GIT_DIR_TEMP/objects/info [ -e $GIT_DIR_ORIG/objects/info/alternates ] && cp $GIT_DIR_ORIG/objects/info/alternates $GIT_DIR_TEMP/objects/info/alternates echo $GIT_DIR_ORIG/objects >> $GIT_DIR_TEMP/objects/info/alternates export GIT_DIR=$GIT_DIR_TEMP

trap "rm -rf $tmp" 0 1 2 3 15

git update-index --add $file || exit 1 tree=`git-write-tree`

rev_arg=`GIT_DIR=$GIT_DIR_ORIG git-rev-parse --default HEAD --revs-only "$@"`
revs=`GIT_DIR=$GIT_DIR_ORIG git-rev-list $rev_arg`
for i in $revs; do
    git diff-tree --name-status $i -C $tree | grep $file |
    sed "s/^/$i:/"
done
Junio C Hamano· Nov 22, 2005, 22:42 UTC · re: Santi Béjar · lore

finding similar blobs (was: Re: $Revision$ keyword replacement?

Santi Béjar <sbejar@gmail.com> writes:
>         How similar this file is to the file $path in these commit(s)?
Very cute.
> tmp=`mktemp -t -d git-find-sim.XXXXXXX`
> ...
> git update-index --add $file || exit 1
> tree=`git-write-tree`

Are you going through all this trouble just to avoid a blob and a tree object left dangling after you are done? Or is there something else going on?

Show 6 quoted lines
> rev_arg=`GIT_DIR=$GIT_DIR_ORIG git-rev-parse --default HEAD --revs-only "$@"`
> revs=`GIT_DIR=$GIT_DIR_ORIG git-rev-list $rev_arg`
> for i in $revs; do
>     git diff-tree --name-status $i -C $tree | grep $file |
>     sed "s/^/$i:/"
> done
Perhaps
        GIT_DIR=$GIT_DIR_ORIG git-rev-list $rev_arg |
        while read one
            git diff-tree --name-status -r $one -C $tree | grep $file |
            sed "s/^/$one:/"
        done

just in case the similar file you will discover is hidden in a subdirectory?

Santi Bejar· Nov 22, 2005, 23:10 UTC · re: Junio C Hamano · lore

Re: finding similar blobs (was: Re: $Revision$ keyword replacement?

2005/11/22, Junio C Hamano <junkio@cox.net>:
> Santi Béjar <sbejar@gmail.com> writes:
>
Show 9 quoted lines
>
> > tmp=`mktemp -t -d git-find-sim.XXXXXXX`
> > ...
> > git update-index --add $file || exit 1
> > tree=`git-write-tree`
>
> Are you going through all this trouble just to avoid a blob and
> a tree object left dangling after you are done?  Or is there
> something else going on?

No, there is nothing else. These are "easy" avoided, so why have these dangling {blob,tree,...}s?

Show 18 quoted lines
>
> > rev_arg=`GIT_DIR=$GIT_DIR_ORIG git-rev-parse --default HEAD --revs-only "$@"`
> > revs=`GIT_DIR=$GIT_DIR_ORIG git-rev-list $rev_arg`
> > for i in $revs; do
> >     git diff-tree --name-status $i -C $tree | grep $file |
> >     sed "s/^/$i:/"
> > done
>
> Perhaps
>
>         GIT_DIR=$GIT_DIR_ORIG git-rev-list $rev_arg |
>         while read one
>             git diff-tree --name-status -r $one -C $tree | grep $file |
>             sed "s/^/$one:/"
>         done
>
> just in case the similar file you will discover is hidden in a
> subdirectory?
Oops :)
Santi
Junio C Hamano· Nov 22, 2005, 23:40 UTC · re: Santi Bejar · lore

Re: finding similar blobs (was: Re: $Revision$ keyword replacement?

Santi Bejar <sbejar@gmail.com> writes:
> No, there is nothing else. These are "easy" avoided, so why have these
> dangling {blob,tree,...}s?
Only because I am lazy ;-).

← back to recent threads