From: David A Cobb <superbiskit@cox.net>
To: Git Mailing List <git@vger.kernel.org>
Subject: Subdividing an existing Repository
Date: Mon, 7 Sep 2015 20:29:07 -0400 [thread overview]
Message-ID: <55EE2BD3.1060300@cox.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
Several Repositories I'm interested in, e.g. MINGW-PACKAGES@GITHUB,
contain multiple "products." Usually, I'm only interested in one or two.
I want to have a local repo with, e.g. iodbc from MinGW-Packages as
sub-moules. I don't even need to keep local content for many of the
other included products. But, I need to keep synchronized with the
upstream, so I don't want to destroy the meta-data that allows me to do
that.
It's not certain at this point that I will ever be invited to push what
I have done up the food chain. Maybe it will always be a private fork.
I've looked at Subtrees and Submodules in the ProGit book. I can see
how to use an existing submodule, but not how to isolate one out of a
larger body of code.
TIA
[-- Attachment #2: superbiskit.vcf --]
[-- Type: text/x-vcard, Size: 121 bytes --]
begin:vcard
fn:David A Cobb
n:Cobb;David A
email;internet:superbiskit@cox.net
x-mozilla-html:TRUE
version:2.1
end:vcard
reply other threads:[~2015-09-08 0:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55EE2BD3.1060300@cox.net \
--to=superbiskit@cox.net \
--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).