Dear diary, on Tue, Apr 19, 2005 at 03:48:43PM CEST, I got a letter
where Ingo Molnar <[EMAIL PROTECTED]> told me that...
> is there any 'export commit as patch' support in git-pasky? I didnt find
> any such command (maybe it got added meanwhile), so i'm using the 'ge'
> hack below.
>
> e.g. i typically look at commits via 'git log', and then when i see
> something interesting, i look at the commit via the 'ge' script. E.g.
> "ge 834f6209b22af2941a8640f1e32b0f123c833061" done in the kernel tree
> will output a particular commit's header and the patch.
Nice idea. I will add it, probably as 'git patch'.
> TREE1=$(cat-file commit 2>/dev/null $1 | head -4 | grep ^tree | cut -d' ' -f2)
> if [ "$TREE1" = "" ]; then echo 'ge <commit-ID>'; exit -1; fi
> PARENT=$(cat-file commit 2>/dev/null $1 | head -4 | grep ^parent | cut -d' '
> -f2)
> if [ "$PARENT" = "" ]; then echo 'ge <commit-ID>'; exit -1; fi
> TREE2=$(cat-file commit 2>/dev/null $PARENT | head -4 | grep ^tree | cut -d'
> ' -f2)
> if [ "$TREE2" = "" ]; then echo 'ge <commit-ID>'; exit -1; fi
commit-id and parent-id tools might be useful. ;-)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
-
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
