From: Tim Mazid <timmazid@hotmail.com>
To: git@vger.kernel.org
Subject: Re: 2 projects 1 repo
Date: Wed, 28 Oct 2009 05:19:40 -0700 (PDT) [thread overview]
Message-ID: <26093640.post@talk.nabble.com> (raw)
In-Reply-To: <25530063.post@talk.nabble.com>
twzgerald wrote:
>
> I have a client-server project where I split them into 2 projects to
> separately create the client in one software project and the server in
> another. I registered myself a project hosting at sourceforge.net which
> provides a git repository. How can I put the 2 projects into the git
> repository.
>
> I want to create some sort of hierarchy like <main-project>--> Client -->
> src --> org.project.client...etc..
>
> |
>
> +----------> Server --> src --> org.project.server...etc..
>
You could simply create two branches, master-server, and master-client, and
just never ever cross-merge them, or their child branches.
Or you just create two repos.
Good luck,
Tim.
--
View this message in context: http://www.nabble.com/2-projects-1-repo-tp25530063p26093640.html
Sent from the git mailing list archive at Nabble.com.
parent reply other threads:[~2009-10-28 12:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <25530063.post@talk.nabble.com>]
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=26093640.post@talk.nabble.com \
--to=timmazid@hotmail.com \
--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 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).