git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Shani Fridman <Shani.Fridman@visionmap.com>,
	"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: submodules : switching to an older commit/Tag in project with submodules
Date: Thu, 16 Aug 2018 20:41:58 +0200	[thread overview]
Message-ID: <87d0uiqhl5.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqr2iydvk2.fsf@gitster-ct.c.googlers.com>


On Thu, Aug 16 2018, Junio C Hamano wrote:

> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> On Thu, Aug 16, 2018 at 12:54 PM, Shani Fridman
>> <Shani.Fridman@visionmap.com> wrote:
>>>
>>> Hi everybody,
>>>
>>> I've got a question regarding submodules -
>>>
>>> I'm working on a git project with submodules connected to it, and pulling changes from them every month (more or less).
>>> Sometimes I need to checkout older versions of the project (tags or specific commits), that needs the older versions of the submodules as they were when I defined the tag. The problem is, that the checkout only changes the superProject directories, and not the submodules... I have to checkout the relevant submodules commit manually.
>>>
>>> Have you came across the same problem? Any idea what can I do?
>>
>> You run "git submodule update".
>
> The problem is, some people consider that I have to do things
> "manually" X-<.

I may be wrong, but I read that part as e.g. cd-ing into each submodule
dir, and checking out the commit you see in "git diff" from the
top-level, hence the suggestion.

      reply	other threads:[~2018-08-16 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 10:54 submodules : switching to an older commit/Tag in project with submodules Shani Fridman
2018-08-16 14:56 ` Stefan Beller
2018-08-16 18:13 ` Ævar Arnfjörð Bjarmason
2018-08-16 18:18   ` Junio C Hamano
2018-08-16 18:41     ` Ævar Arnfjörð Bjarmason [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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=87d0uiqhl5.fsf@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=Shani.Fridman@visionmap.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).