From: "Pat Maddox" <pergesu@gmail.com>
To: git@vger.kernel.org
Subject: Re: Submodules and branches
Date: Fri, 4 Apr 2008 13:07:16 -0700 [thread overview]
Message-ID: <810a540e0804041307l665442eapcb5547343358df04@mail.gmail.com> (raw)
In-Reply-To: <32541b130804041302i1e32e4b3l141e8b08200a2357@mail.gmail.com>
On Fri, Apr 4, 2008 at 1:02 PM, Avery Pennarun <apenwarr@gmail.com> wrote:
> On 4/4/08, Pat Maddox <pergesu@gmail.com> wrote:
> > I've got a repository that uses submodules. If I cd to the repo root
> > and create a branch, all the submodules are switched to that branch as
> > well. All good so far. I go into the submodules and do my work,
> > committing as I go along. Then when I'm all done and want to merge
> > the changes into my master branch, I cd back to the repo root and do
> > "git merge new_topic"
> >
> > That's where it breaks down. The commits that I made go into the
> > master repo itself, and the submodules don't have them.
>
> There is something wrong with your story somewhere: submodules in git
> each have their own, completely independent,
> branching/merging/pulling/pushing etc. What makes you think the
> submodules are branching at the same time as your supermodule?
>
> Perhaps you have accidentally committed the *files* from your
> submodule into your supermodule, which means you're not using
> git-submodule at all.
Hi Avery,
You're right, something was screwed up with the repo. One of the
paths was added as a submodule, but it also had files committed to it.
I fixed all of that up and it seems to be fine now.
Pat
next prev parent reply other threads:[~2008-04-04 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 19:40 Submodules and branches Pat Maddox
2008-04-04 20:02 ` Avery Pennarun
2008-04-04 20:07 ` Pat Maddox [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-25 0:41 submodules " Stephen Hemminger
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=810a540e0804041307l665442eapcb5547343358df04@mail.gmail.com \
--to=pergesu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.