From: Robert Pollak <robert.pollak@jku.at>
To: Daniel <daniel@netwalk.org>
Cc: git <git@vger.kernel.org>, apenwarr@gmail.com
Subject: Re: dependable submodules
Date: Mon, 21 Mar 2011 17:18:56 +0100 [thread overview]
Message-ID: <4D877A70.8070907@jku.at> (raw)
In-Reply-To: <AANLkTin8Mr5xLtLqHSVuEOzzfmqnR2LU5vDdVfPprNXn@mail.gmail.com>
On 2011-03-20 Daniel wrote:
[...]
> So would it be correct to say that even though those files are
> remotely fetched on a clone of the repository, they are actually
> revisioned and stored in the super project?
You might want to try Avery Pennarun's git-subtree, which seems to
provide this functionality.
It's at https://github.com/apenwarr/git-subtree.
next prev parent reply other threads:[~2011-03-21 16:27 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
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 [this message]
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=4D877A70.8070907@jku.at \
--to=robert.pollak@jku.at \
--cc=apenwarr@gmail.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).