From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: git@vger.kernel.org
Subject: submodules and branches
Date: Thu, 24 Apr 2008 17:41:42 -0700 [thread overview]
Message-ID: <20080424174142.5dbb6ae3@speedy> (raw)
Our CM team likes to use both submodules and branches and it doesn't
always work cleanly. Some examples:
1. The new release on branch "next_release" adds a submodule, but then the
submodule shows up on all branches including the production branch.
2. For next release on branch "next_release" a submodule was renamed by
moving the target directory, but now git submodule update makes two copies.
Git generally does a good job of tracking renames and deletions, so the fact
that submodules leave stuff behind is surprising.
next reply other threads:[~2008-04-25 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 0:41 Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-04 19:40 Submodules and branches Pat Maddox
2008-04-04 20:02 ` Avery Pennarun
2008-04-04 20:07 ` Pat Maddox
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=20080424174142.5dbb6ae3@speedy \
--to=stephen.hemminger@vyatta.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).