BUG simple "revert" fails

Anthony Booker· Aug 16, 2008, 23:21 UTC · lore

Attached is a tarball with a couple of repositories. eg-sub is a submodule in eg. In eg there's a commit, cd626e6baaa0888c6090e1f040f9f0ba8bfef218, which inappropriately changed a file in eg-sub. It's a newby mistake with git and submodules.

The problem is that the problem can't be reverted. It fails with unknown object It is a submodule.

To reproduce, unpack the tarball, cd to eg and: git revert cd626e6baaa0888c6090e1f040f9f0ba8bfef218

Thanks for your time.

Michael J Gruber· Aug 18, 2008, 09:14 UTC · re: Anthony Booker · lore

Re: BUG simple "revert" fails

Anthony Booker venit, vidit, dixit 17.08.2008 01:21:

Show 12 quoted lines

> Attached is a tarball with a couple of repositories.  eg-sub is a 
> submodule in eg.  In eg there's a commit, 
> cd626e6baaa0888c6090e1f040f9f0ba8bfef218, which inappropriately changed 
> a file in eg-sub.  It's a newby mistake with git and submodules.
> 
> The problem is that the problem can't be reverted.  It fails with 
> unknown object It is a submodule.
> 
> To reproduce, unpack the tarball, cd to eg and:
> git revert cd626e6baaa0888c6090e1f040f9f0ba8bfef218
> 
> Thanks for your time.

There's no tarball attached, at least not when reading your post via gmane.

If the repo hasn't been published yet you probably want to rewrite history rather than introducing a revert commit.

Revering is a bit complicated because the commit to be reverted contains: subproject commit (unregistering from sub in super) plus add commit (in super).

Michael