From: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
To: git@vger.kernel.org
Subject: Re: Issues when changing submodule URLs
Date: Fri, 15 Aug 2008 17:01:29 +0200 [thread overview]
Message-ID: <48A59A49.9030305@fastmail.fm> (raw)
In-Reply-To: <d3af73dc0808150537r1f708bct14113943d741e653@mail.gmail.com>
Gerard Lledó venit, vidit, dixit 15.08.2008 14:37:
> We are using a super repository for our development where all our code
> resides inside submodules. I'm maintaining this tree, so it's quite
> common that I change a submodule to point to a different URL according
> to our needs (ie, another developer is now in charge of one module).
>
> So, basically I delete the old submodule "rm -rf module && git rm
> module", tune .gitmodules and add it again from a different location
> "git submodule add ssh://server/newpath module".
>
> The problem comes when another developer pulls the super repository
> from me and he already has the old module URL initialized/updated.
> What is a safe/obvious update path for him? "git submodule update"
> does not work and running init/update doesn't help neither.
> Is there any way for me to ease these tasks for the rest of developers?
>
> I know one option is to keep the URLs untouched and then merge trees
> as needed, but this seems to be a bigger workload for everyone.
How about:
- You mirror the submodule repos.
- Your superproject references the mirrors.
- In your mirror configuration, use descriptive names rather than actual
URLs for the origin of the mirror.
- Use "url.realurl.insteadOf descriptivename" in your own config, which
can be changed easily whenever the authoritative source of a submodule
changes (see git config).
Cheers,
Michael
prev parent reply other threads:[~2008-08-15 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 12:37 Issues when changing submodule URLs Gerard Lledó
2008-08-15 15:01 ` Michael J Gruber [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48A59A49.9030305@fastmail.fm \
--to=michaeljgruber+gmane@fastmail.fm \
--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.