git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Keeping <john@keeping.me.uk>
To: "Odin Hørthe Omdal" <odinho@opera.com>
Cc: git@vger.kernel.org
Subject: Re: git submodule update needs to be at the toplevel of working tree, why?
Date: Fri, 22 Nov 2013 13:47:47 +0000	[thread overview]
Message-ID: <20131122134747.GC15033@serenity.lan> (raw)
In-Reply-To: <1385126550.10973.50760825.6B70B959@webmail.messagingengine.com>

On Fri, Nov 22, 2013 at 02:22:30PM +0100, Odin Hørthe Omdal wrote:
> I'm usually in a subfolder doing actual work. A very common problem I
> have is wanting to do a submodule update, but git really hates that. And
> I wonder why?
> 
> It wouldn't be hard to cd to the toplevel working directory, do the
> update, and cd back. It's what I have to do manually every time now
> already:

This restriction was removed in Git 1.8.4.

  reply	other threads:[~2013-11-22 13:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 13:22 git submodule update needs to be at the toplevel of working tree, why? Odin Hørthe Omdal
2013-11-22 13:47 ` John Keeping [this message]
2013-11-22 14:37   ` Odin Hørthe Omdal

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=20131122134747.GC15033@serenity.lan \
    --to=john@keeping.me.uk \
    --cc=git@vger.kernel.org \
    --cc=odinho@opera.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.
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).