From: Alan Edwards <kae@xnet.com>
To: git@vger.kernel.org
Subject: How to reorganize git tree
Date: Thu, 26 Jan 2012 13:35:05 -0500 [thread overview]
Message-ID: <20120126133505.it34vehs0044o848@webmail.xnet.com> (raw)
I was new to git about a year ago and created a git directory
structure containing several different projects like:
/source/web_server1/project1
/source/web_server1/project2
/source/web_server1/project3
/source/web_server1/project4
/source/web_server2/project5
/source/web_server2/project6
where my massive .git repository is:
/source/.git (containing all the projects on all the web servers....
Oops!) There seems to be lots of "loose objects".
Somewhere along the way I figured out that this probably wasn't a good
idea and I ended up making a git repository under one of the projects:
/source/web_server1/project4/.git
Not sure if that was the best decision either. I've already checked in
changes to the /source/web_server1/project4/.git repository for
project4 and I've checked in changes to project2 into the /source/.git
repository.
Of course I now realize the errors of my way and would like to restructure.
the only changes that have been checked into the big upper level
repository are changes for project2. Is it possible to carve out
those changes from the /source/.git repository and create a new
/source/web_server1/project2/.git repository?
Maybe the way to deal with this is to remove the other directories
from the /source/.git repository and leave project2 there.
Any one have any suggestions?
I'm not sure if I'm posting this in the right place (I'm at work and
they don't allow access to many places and I don't have access to the
news group).
Thanks!
-Alan Edwards
kae at xnet dot com (my home email address)
next reply other threads:[~2012-01-26 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 18:35 Alan Edwards [this message]
2012-01-26 18:57 ` How to reorganize git tree Ben Walton
2012-01-26 23:27 ` Jakub Narebski
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=20120126133505.it34vehs0044o848@webmail.xnet.com \
--to=kae@xnet.com \
--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).