From: Junio C Hamano <gitster@pobox.com>
To: Daniel <daniel@netwalk.org>
Cc: git <git@vger.kernel.org>
Subject: Re: dependable submodules
Date: Sat, 19 Mar 2011 21:27:58 -0700 [thread overview]
Message-ID: <7vd3lmv2k1.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <AANLkTi=JVO+KhnLKR-PvNQQFaZLhUmiVbKFxuytYEpmc@mail.gmail.com> (daniel@netwalk.org's message of "Sat, 19 Mar 2011 17:53:26 -0700")
Daniel <daniel@netwalk.org> writes:
> IOW, I may have
>
> myrepo/somefile.txt
> myrepo/another_project/.git/...
> myrepo/another_project/another_project_file.txt
>
> and I'd like to, when I clone repo, to be able to get all files from
> repo independently of the remote repo's existence.
Cloned repositories from your repository can say where they get from
"another_project" embedded in it in .git/config of the clone of the
superproject. The supermodule may have .gitmodules that points at github
or whereever your original upstream repository resided, but that is
supposed to be used to only give you the default.
When "another_project" you borrowed really dies and becomes useless for
anybody, you may update its entry in .gitmodules of the superproject to
point at the public repository that inherited that submodule project.
The project might be simply abandoned, in which case you end up being
that inheritor.
next prev parent reply other threads:[~2011-03-20 4:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 0:53 dependable submodules Daniel
2011-03-20 4:27 ` Junio C Hamano [this message]
2011-03-20 4:32 ` Daniel
2011-03-20 12:36 ` Jens Lehmann
2011-03-20 16:06 ` Daniel
2011-03-21 16:18 ` Robert Pollak
2011-03-22 3:56 ` Daniel
2011-03-22 5:13 ` Avery Pennarun
2011-03-22 14:28 ` in-gitvger
2011-03-22 14:55 ` Daniel
2011-03-22 18:56 ` Jens Lehmann
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=7vd3lmv2k1.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=daniel@netwalk.org \
--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).