Re: New User Question

From: Joel McGahen <vin4bacchus@me.com>
Date: Jun 17, 2013, 16:56 UTC
Message-ID: <1786A257-B21A-46CC-8F41-31AE9B948C00@me.com>
In-Reply-To: <CABjHNoSfLGW_D8RM8+LghP8kKYsYhZKi=7k4kEJSNEX=PDe2XQ@mail.gmail.com>

Thanks William. You response is much appreciated.

Should I have just changed the origin URL in the first place to point to my new local repo? What I did was to just add another remote with a different name (temp_repo). So if I do "git remote" I see origin and temp_repo. I then pushed to "temp_repo".

Or should I have pushed as I did and then change the origin to the new repo location? So If I would "git remote" i would still only see one (origin) but it would point towards the temp_repo location?

On Jun 17, 2013, at 12:51 PM, William Swanson <swansontec@gmail.com> wrote:

Show 9 quoted lines

> On Mon, Jun 17, 2013 at 8:39 AM, Joel McGahen <vin4bacchus@me.com> wrote:
>> 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.
> 
> Git stores information about remotes in the .git/config file. You can
> either edit this file directly to change which URL "orgin" points to,
> or you can use the "git remote" commands to make the same changes. You
> can read the documentation by typing "git help remote".