From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Joel McGahen <vin4bacchus@me.com>
Cc: git@vger.kernel.org
Subject: Re: New User Question
Date: Mon, 17 Jun 2013 19:07:53 +0200 [thread overview]
Message-ID: <20130617170753.GD25488@paksenarrion.iveqy.com> (raw)
In-Reply-To: <F201B6D6-7A69-4DD6-BDF5-5AE12E3A176C@me.com>
On Mon, Jun 17, 2013 at 11:39:44AM -0400, Joel McGahen wrote:
> I have a question about GIT remote repos. Here is my scenario.
>
> 1. Work client has a repo (origin, branch of master).
> 2. Due to contractual issues I need to host a remote copy of this repo that my developers can utilize while we get the contractual issues resolved as development must continue.
> 3. I have a virtual machine from the client which already has a remote of origin setup.
> 4. I have created a bare repo on a server my developer's have access to.
> 5. I have added that remote to my copy of the client VM local repo and pushed its contents to my newly created bare repo.
>
> What I need to understand is how to
> a) Connect my developer's VM local repos to the new remote repo I created so they can continue to work.
> b) Once the contractual issues are resolved reconnect the developer's local repos back to the original orgin/master repo and merge all their changes.
>
> I'm fairly new to GIT but have worked with version control for a long time (CVS, PVCS, Subversion etc).
>
> Any help would be greatly appreciated!
Hi!
The short answer is: git remote add (and git help remote for
details). It's also possible to manally edit .git/config if it's
basically just a adress change you're doing.
The long answer is harder. You've experience with centralized systems.
Remember that git is decentralized. Every developer you've is a fully
functional unit on his own. All you need is a way for the developers to
interact with eachothers. It can be done via e-mail, or with them
pulling from eachother directly or as you've done, with one central
repository that everyone sync to.
The questions you've is rather fundamental to git. I tells me that you
do not fully utilize the strengths of git. I suggest reading the
progit book.
Good luck!
--
Med vänliga hälsningar
Fredrik Gustafsson
tel: 0733-608274
e-post: iveqy@iveqy.com
prev parent reply other threads:[~2013-06-17 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 15:39 New User Question Joel McGahen
2013-06-17 16:51 ` William Swanson
2013-06-17 16:56 ` Joel McGahen
2013-06-17 17:19 ` William Swanson
2013-06-17 17:07 ` Fredrik Gustafsson [this message]
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=20130617170753.GD25488@paksenarrion.iveqy.com \
--to=iveqy@iveqy.com \
--cc=git@vger.kernel.org \
--cc=vin4bacchus@me.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).