On Mon, Apr 12, 2010 at 10:47 AM, Shawn O. Pearce <spearce@xxxxxxxxxxx> wrote: > Tim Visher <tim.visher@xxxxxxxxx> wrote: >> I recently began to use submodules to manage large packages that I >> depend on from my .emacs file and I've run into an issue where I made >> a change locally and didn't push out to the master repo. I'm now not >> at that box and I'm trying to checkout the repo fresh. >> >> The problem is that the master repo doesn't have the commit specified… >> Where? So I can't edit the submodule commit and then readd it because >> I don't have the submodule to edit since I can't check it out. Is it >> possible to just manually munge the commit that the submodule is >> pointing to? > > Yup: > > git update-index --cacheinfo 160000 commit path Thanks, Shawn. That worked great. -- In Christ, Timmy V. http://burningones.com/ http://five.sentenc.es/ - Spend less time on e-mail -- 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