git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Visher <tim.visher@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Manually edit the commit a submodule is pointing to?
Date: Mon, 12 Apr 2010 14:19:15 -0400	[thread overview]
Message-ID: <g2yc115fd3c1004121119l404caf8coa376d7561f130a3b@mail.gmail.com> (raw)
In-Reply-To: <20100412144718.GC6313@spearce.org>

On Mon, Apr 12, 2010 at 10:47 AM, Shawn O. Pearce <spearce@spearce.org> wrote:
> Tim Visher <tim.visher@gmail.com> 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

      reply	other threads:[~2010-04-12 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 14:31 Manually edit the commit a submodule is pointing to? Tim Visher
2010-04-12 14:47 ` Shawn O. Pearce
2010-04-12 18:19   ` Tim Visher [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=g2yc115fd3c1004121119l404caf8coa376d7561f130a3b@mail.gmail.com \
    --to=tim.visher@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).