From: Avery Pennarun <apenwarr@gmail.com>
To: John Dlugosz <JDlugosz@tradestation.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: submodule problem
Date: Fri, 19 Mar 2010 13:27:42 -0400 [thread overview]
Message-ID: <32541b131003191027p2fbb358fvb86b7c6f18de64cc@mail.gmail.com> (raw)
In-Reply-To: <89030B4A18ECCD45978A3A6B639D1F2403299C8395@FL01EXMB01.trad.tradestation.com>
On Fri, Mar 19, 2010 at 12:54 PM, John Dlugosz
<JDlugosz@tradestation.com> wrote:
> I thought I knew what I was doing, after reading the instructions.
>
> When I checked out an older version of the main project, I have to sync to the proper
> (older) version of the submodule too. git admonished me to run the command from
> the toplevel of the working tree, and when that was done,
>
> git submodule update
>
> gives no output.
>
> git submodule status
Did you run 'git submodule init'? You generally have to do this once per repo.
Avery
next prev parent reply other threads:[~2010-03-19 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 16:54 submodule problem John Dlugosz
2010-03-19 17:27 ` Avery Pennarun [this message]
2010-03-19 17:29 ` Lars Hjemli
2010-03-19 19:22 ` John Dlugosz
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=32541b131003191027p2fbb358fvb86b7c6f18de64cc@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=JDlugosz@tradestation.com \
--cc=git@vger.kernel.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).