On 1 May 2012, Darrell Anderson verbalised:

>> This is a right terminological mess, I must admit.
>
> I don't know how this is supposed to work. I ran 'git reset --hard'.
> When I viewed the top level with git log, the newest date was April
> 10. Seemed okay to me.
>
> After my previous two builds and testing I wondered whether that truly
> reset the source files. I changed to the tdebase directory and again
> ran git log. The most recent commit was from a few days ago.
>
> So I did a git reset there too and in tdelibs.

Oh, you'll need to do a 'git submodule update --recursive' after
resetting the containing repository to catch the submodules in the reset
net, too. Submodules are not instantly affected by motion through
history in the parent (which I consider a bug, but which was essential
if submodules were not to be so invasive that they'd never have been
accepted into git).

-- 
NULL && (void)