From: Avery Pennarun <apenwarr@gmail.com>
To: "S. M. Ibrahim (Lavlu)" <smibrahim@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: hosting multiple project in single git repository
Date: Wed, 13 May 2009 13:58:28 -0400 [thread overview]
Message-ID: <32541b130905131058i54dfa56ck8938aab96cb1d442@mail.gmail.com> (raw)
In-Reply-To: <4997275b0905131048t1b5c1427w85a2f96964ea16b6@mail.gmail.com>
On Wed, May 13, 2009 at 1:48 PM, S. M. Ibrahim (Lavlu)
<smibrahim@gmail.com> wrote:
> 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
next prev parent reply other threads:[~2009-05-13 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4997275b0905131031q3c572854r4b0a899ca43063be@mail.gmail.com>
[not found] ` <4997275b0905131046s407e334ag6783a6365c89fe10@mail.gmail.com>
2009-05-13 17:48 ` hosting multiple project in single git repository S. M. Ibrahim (Lavlu)
2009-05-13 17:58 ` Avery Pennarun [this message]
2009-05-14 7:14 ` S. M. Ibrahim (Lavlu)
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=32541b130905131058i54dfa56ck8938aab96cb1d442@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=smibrahim@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).