From: "Stewart A. Brown" <sabrown256@sbcglobal.net>
To: git@vger.kernel.org
Subject: Site dependent repositories
Date: Sat, 20 Aug 2011 20:31:17 -0700 [thread overview]
Message-ID: <4E507C05.2090700@sbcglobal.net> (raw)
I am wondering whether or not git has the functionality to handle
my situation.
I have git repositories at multiple sites. At each site the git repository
has site dependent sources. Each repository is organised something
like:
top/a/local
b
c/d/extensions
e
The directories top, a, b, c, d, and e have sources that need to be
pushed or pulled between the repositories at all sites. The directories
'local' and 'extensions' have sources that must be managed within sites
but never pushed or pulled between sites.
The ignore mechanism will not suffice because the files in 'local' and
'extensions' must be source managed. I have looked a bit into
submodules, filters, and hooks. None of these jumps out as obvious, but
they are rich mechanisms with plenty of subtleties.
Does git have a way of letting me do this?
Stewart Brown
sabrown256@gmail.com
next reply other threads:[~2011-08-21 3:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 3:31 Stewart A. Brown [this message]
2011-08-21 4:21 ` Site dependent repositories Andrew Keller
2011-08-21 5:46 ` Evan Shelhamer
2011-08-21 16:14 ` 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=4E507C05.2090700@sbcglobal.net \
--to=sabrown256@sbcglobal.net \
--cc=git@vger.kernel.org \
--cc=sabrown256@gmail.com \
/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).