From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Eyvind Bernhardsen" <eyvind-git@orakel.ntnu.no>
Cc: "Sam Vilain" <sam@vilain.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git-submodule getting submodules from the parent repository
Date: Sun, 30 Mar 2008 19:03:27 -0400 [thread overview]
Message-ID: <32541b130803301603u65d1b6b6ladac0f6200433e5f@mail.gmail.com> (raw)
In-Reply-To: <C38585A9-F09C-4A5B-8E72-6F3127DB2BB9@orakel.ntnu.no>
On Sun, Mar 30, 2008 at 3:50 PM, Eyvind Bernhardsen
<eyvind-git@orakel.ntnu.no> wrote:
> Pushing to a branch works except that I couldn't figure out what to do
> if the push doesn't succeed, ie, the branch has advanced on the remote
> end. That's a problem if more than one module references the
> submodule or there are multiple branches in the main module.
That's easy: just error out in that case. If the current system would
just error out when I screwed up, I'd at least be able to deal with
it. Right now I silently create un-check-outable parent repositories
because I failed silently to upload my latest checkins to the child
repository.
> True :) I still have no idea how to figure out which submodules are
> dirty, though. Solving that will enable a safe "submodule update",
> which I think is more important than "submodule push".
What is unsafe about "submodule update"?
Thanks,
Avery
next prev parent reply other threads:[~2008-03-30 23:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 22:35 git-submodule getting submodules from the parent repository Avery Pennarun
2008-03-29 23:22 ` Sam Vilain
2008-03-30 13:32 ` Eyvind Bernhardsen
2008-03-30 17:48 ` Sam Vilain
2008-03-30 19:50 ` Eyvind Bernhardsen
2008-03-30 20:19 ` Sam Vilain
2008-03-31 10:05 ` Eyvind Bernhardsen
2008-03-30 23:03 ` Avery Pennarun [this message]
2008-03-31 9:29 ` Eyvind Bernhardsen
2008-03-31 21:36 ` Avery Pennarun
2008-04-01 23:05 ` Sam Vilain
2008-04-01 23:56 ` Avery Pennarun
2008-04-02 0:35 ` Junio C Hamano
2008-04-02 2:03 ` Avery Pennarun
2008-04-02 20:06 ` Sam Vilain
2008-04-02 21:32 ` Junio C Hamano
2008-03-30 23:00 ` Avery Pennarun
2008-04-01 23:10 ` Sam Vilain
2008-03-31 6:22 ` Johannes Sixt
2008-03-31 21:24 ` Avery Pennarun
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=32541b130803301603u65d1b6b6ladac0f6200433e5f@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=eyvind-git@orakel.ntnu.no \
--cc=git@vger.kernel.org \
--cc=sam@vilain.net \
/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).