From: Jonathan Nieder <jrnieder@gmail.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Oliver Kullmann <O.Kullmann@swansea.ac.uk>,
Seth Robertson <in-gitvger@baka.org>,
git@vger.kernel.org
Subject: Re: how to update a submodule?
Date: Sun, 2 Jan 2011 11:57:26 -0600 [thread overview]
Message-ID: <20110102175725.GC13358@burratino> (raw)
In-Reply-To: <4D20B629.8000107@web.de>
Jens Lehmann wrote:
> Submodules don't work very well when you change URLs (that can result
> in forcing your coworkers to do a "git submodule sync" in their repo
> every time they switch to a commit with a changed URL).
For the future, it is probably most convenient to use URLs starting
with "../" or "./", which would rarely need to change. That can even
work with passing around a tarball of bundles and a script to
reconstitute them, I think.
Thanks for some food for thought.
Jonathan
prev parent reply other threads:[~2011-01-02 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 22:24 how to update a submodule? Oliver Kullmann
2010-12-31 23:42 ` Seth Robertson
2011-01-01 20:39 ` Oliver Kullmann
2011-01-02 11:30 ` Jens Lehmann
2011-01-02 15:55 ` Oliver Kullmann
2011-01-02 17:30 ` Jens Lehmann
2011-01-02 17:57 ` Jonathan Nieder [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=20110102175725.GC13358@burratino \
--to=jrnieder@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=O.Kullmann@swansea.ac.uk \
--cc=git@vger.kernel.org \
--cc=in-gitvger@baka.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).