From: Phil Hord <hordp@cisco.com>
To: "Paulo J. Matos" <pocmatos@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Special branch for remote
Date: Wed, 27 Jul 2011 10:35:21 -0400 [thread overview]
Message-ID: <4E302229.4030402@cisco.com> (raw)
In-Reply-To: <j0ohjr$fcd$1@dough.gmane.org>
On 07/27/2011 04:18 AM, Paulo J. Matos wrote:
> Hi all,
>
> I have a huge repository for a software I am developing. In it I have
> source code, docs, experiments, tests, etc. However, I want to push
> only the src/ to the github remote, nothing else. What's the best way
> to achieve this. Do I need to simply create a new branch and then push
> the new branch to github or there's anything else involved that I need
> to know?
>
Yes, you can do this with branches. See [1] for an example of a similar
workflow.
You can also manage this with submodules [2] or subtree-merge [3].
I prefer submodules since it keeps the huge stuff (docs and bins) away
from my source code and makes my source code repo much more responsive.
[1] http://www.braintreepayments.com/devblog/our-git-workflow
[2] http://progit.org/book/ch6-6.html
[3] http://progit.org/book/ch6-7.html
HTH,
Phil
next prev parent reply other threads:[~2011-07-27 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 8:18 Special branch for remote Paulo J. Matos
2011-07-27 14:35 ` Phil Hord [this message]
2011-07-27 14:36 ` Paulo J. Matos
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=4E302229.4030402@cisco.com \
--to=hordp@cisco.com \
--cc=git@vger.kernel.org \
--cc=pocmatos@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).