On Thursday 2006 October 26 18:33, Andy Whitcroft wrote:

quoted text
> If we are changing the format would it not make more sense to be in the
> same order as the tool that lets you use it?
>
> I thought that was git cat-file <type> <commit-ish>

The only problem with that is that the type string is of variable width, while 
the hash is fixed; hence <hash> <type> is more visually appealing than <type> 
<hash>.

Does it really matter anyway?  Some sort of processing would have to happen 
before using git-prune output as git-cat-file parameters...

git-prune -n |
while read hash type
do
 git-cat-file $type $hash
done



Andy

-- 
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html