On Mon, 2005-04-18 at 12:27 +0200, Petr Baudis wrote:
> Yes. As far as I'm concerned, I'd put such stuff to git log, and extend
> it usage so that it is possible to print individual log entries with it
> - just make it accept a _range_ of commits, and then do
>
> git log $commit $commit
That's fairly trivial. In the current (and misguided) version with
chronological output, rev-tree will do it all for you, in fact:
rev-tree $1 ^$2
In the older and more useful version, it was only slightly more complex:
base=$(gitXnormid.sh -c $1) || exit 1
+if [ -n "$2" ]; then
+ endpoint=$(gitXnormid.sh -c $2) || exit 1
+ if rev-tree $base $endpoint | grep -q $base:3; then
+ base=
+ else
+ rev-tree --edges $base $endpoint | sed 's/[a-z0-9]*:1//g' > $TMPCL
+ fi
+fi
changelog $base
rm $TMPCL $TMPCM
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
