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

Re: Questions on 'cvs migration guide''

From
Linus Torvalds <torvalds@osdl.org>
Date
Aug 19, 2005, 04:33 UTC
Message-ID
<Pine.LNX.4.58.0508182130050.3412@g5.osdl.org>
In-Reply-To
<46a038f9050818201717f9ed93@mail.gmail.com>
On Fri, 19 Aug 2005, Martin Langhoff wrote:
Show 5 quoted lines
>
> In the section 'Emulating CVS behaviour', where the team setup is
> described with a team 'merger'. What is not clear is how to deal with
> project-wide branches. Should they be created in the master repo, and
> everyone clone a new repo from it?

Just make them another branch in the master repo. Whether people will clone a whole new repo for it, or have just one repo and switch between local branches in their own local (single) repo is their personal choice. Some people may well prefer to have all different branches checked out in different places (ie have one repository per branch) others may prefer to work with one repository and just switch.

> And yet another question: the teammember who is pulling must 'switch'
> the merging repo to the right branch, pull from the corresponding
> remote repos of each teammember, and push to the public view of the
> repo. Is that right?

.. yes. Or alternatively, just keep the repo at that branch (and if such a person works on multiple branches, he/she can thus just keep multiple repos).

		Linus
Previous: Martin LanghoffNext: Martin Langhoff
Message 2 of 4 in “Questions on 'cvs migration guide''”
  1. Martin LanghoffAug 19, 2005
  2. Linus TorvaldsAug 19, 2005
  3. Martin LanghoffAug 19, 2005
  4. Linus TorvaldsAug 19, 2005

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.