git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Approach for collaborative branches

From
GPGary Pickrell <gary@pickrell.com>
Date
Dec 6, 2009, 18:56 UTC
Message-ID
<4B1BFE41.1040905@pickrell.com>
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:
Show 34 quoted lines
> 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.
>
>   
Previous: Matthieu Moy
Message 3 of 3 in “Approach for collaborative branches”
  1. Gary PickrellDec 6, 2009
  2. Matthieu MoyDec 6, 2009
  3. Gary PickrellDec 6, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.