"Shawn O. Pearce" <spearce@xxxxxxxxxxx> wrote:
> Don Zickus <dzickus@xxxxxxxxx> wrote:
> > Considering git-commit doesn't allow this (probably for good reason),
> > is it technically safe to do the following sequence of events?
> >
> > tree=$(git-write-tree) #basically the same tree HEAD points to
> > commit=$(echo $IDEAS | git-commit-tree $tree -p HEAD)
> > git-update-ref HEAD $commit HEAD
This can also be written shorter, and safer:
head=$(git-rev-parse --verify HEAD^0)
commit=$(echo $IDEAS | git-commit-tree $head^{tree} -p $head)
git-update-ref HEAD $commit $head
The reason you do it like this is it prevents a HEAD which was
modified between the time you did git-commit-tree and git-update-ref
from being lost.
And the write-tree is completely unnecessary, and might actually
write out a dirty-index, which would make your ideas commit actually
modifying files - not what you wanted.
--
Shawn.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html