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

Re: hosting multiple project in single git repository

From
Avery Pennarun <apenwarr@gmail.com>
Date
May 13, 2009, 17:58 UTC
Message-ID
<32541b130905131058i54dfa56ck8938aab96cb1d442@mail.gmail.com>
In-Reply-To
<4997275b0905131048t1b5c1427w85a2f96964ea16b6@mail.gmail.com>

On Wed, May 13, 2009 at 1:48 PM, S. M. Ibrahim (Lavlu) <smibrahim@gmail.com> wrote:

Show 7 quoted lines
> in our company we are moving all our subversion repository to git.
> git-svn is working really nice. but facing a problem. we have one svn
> repository where we hosted two projects and both the projects are
> under development. project a is trunk and project b is branch/xxxx .
> and project b was copied from trunk . we have plan to merge this two
> project in future. what is the best way to maintain this two project
> in git ? should we make to different git repository .

If they both branched from the same place and they might be merged back together someday, then keeping them in the same repository seems rather harmless. And you can always split the repositories later if you want. Similarly, you can check out the same repository in two different local directories on two different branches and it's essentially equivalent to having two repositories in the first place.

What problems are you having with the setup as it is now?
Have fun,
Avery
Previous: S. M. Ibrahim (Lavlu)Next: S. M. Ibrahim (Lavlu)
Message 2 of 3 in “hosting multiple project in single git repository”
  1. S. M. Ibrahim (Lavlu)May 13, 2009
  2. Avery PennarunMay 13, 2009
  3. S. M. Ibrahim (Lavlu)May 14, 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.