From: Gary Pickrell <gary@pickrell.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org
Subject: Re: Approach for collaborative branches
Date: Sun, 06 Dec 2009 10:56:01 -0800 [thread overview]
Message-ID: <4B1BFE41.1040905@pickrell.com> (raw)
In-Reply-To: <vpqhbs4f2gz.fsf@bauges.imag.fr>
Thank you Matthieu,
It did exactly what I wanted and I wouldn't have figured it out by myself.
-Gary
Matthieu Moy wrote:
> Gary Pickrell <gary@pickrell.com> writes:
>
>
>> 1) Clone the repository on Ubuntu
>> 2) Made an Ubuntu branch
>> 3) Made my changes to the code. Added files...ect
>> 4) Used git push origin Ubuntu to push the changes to the repository
>>
>> I'm unable to see my Ubuntu changes on my windows machine. How should
>> I proceed?
>>
>
> On the windows machine, you should do first
>
> git fetch
>
> this will tell you about the new branch if you didn't fetch it
> already. If it's called Ubuntu remotely, it's probably called
> origin/Ubuntu on your local repository after doing a fetch. Therefore,
> you can now do
>
> git merge origin/Ubuntu
>
>
> Now, you probably also want your local branch to be named the same way
> on both machines. One way to do that is to create a branch "foo" on
> the repository, then on both sides, fetch it and do
>
> git checkout --track origin/foo
>
> this will create a local branch foo, and tell git that further "pull"
> should take their changes from origin/foo.
>
>
prev parent reply other threads:[~2009-12-06 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 16:57 Approach for collaborative branches Gary Pickrell
2009-12-06 17:15 ` Matthieu Moy
2009-12-06 18:56 ` Gary Pickrell [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=4B1BFE41.1040905@pickrell.com \
--to=gary@pickrell.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.