{"thread":{"id":"27932","subject":"Special branch for remote","startedAt":"2011-07-27T08:18:03Z","lastAt":"2011-07-27T14:36:28Z","messageCount":3,"participants":["Paulo J. Matos","Phil Hord"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"172138","messageId":"j0ohjr$fcd$1@dough.gmane.org","threadId":"27932","inReplyTo":null,"subject":"Special branch for remote","fromName":"Paulo J. Matos","fromEmail":"pocmatos@gmail.com","sentAt":"2011-07-27T08:18:03Z","receivedAt":"2011-07-27T08:18:03Z","isPatch":false,"sender":{"key":"pocmatos@gmail.com","avatar":"https://gravatar.com/avatar/18a65959cb633850917ac745fd4af17eed7b1f4150d79f9d0f0990dbdca85272?d=mp&s=160"},"body":"Hi all,\n\nI have a huge repository for a software I am developing. In it I have \nsource code, docs, experiments, tests, etc. However, I want to push only \nthe src/ to the github remote, nothing else. What's the best way to \nachieve this. Do I need to simply create a new branch and then push the \nnew branch to github or there's anything else involved that I need to know?\n\nCheers,\n\n-- \nPMatos\n"},{"id":"172162","messageId":"4E302229.4030402@cisco.com","threadId":"27932","inReplyTo":"j0ohjr$fcd$1@dough.gmane.org","subject":"Re: Special branch for remote","fromName":"Phil Hord","fromEmail":"hordp@cisco.com","sentAt":"2011-07-27T14:35:21Z","receivedAt":"2011-07-27T14:35:21Z","isPatch":false,"sender":{"key":"phil.hord@gmail.com","avatar":"https://avatars.githubusercontent.com/u/123908?v=4"},"body":"On 07/27/2011 04:18 AM, Paulo J. Matos wrote:\n> Hi all,\n>\n> I have a huge repository for a software I am developing. In it I have\n> source code, docs, experiments, tests, etc. However, I want to push\n> only the src/ to the github remote, nothing else. What's the best way\n> to achieve this. Do I need to simply create a new branch and then push\n> the new branch to github or there's anything else involved that I need\n> to know?\n>\n\nYes, you can do this with branches. See [1] for an example of a similar\nworkflow.\n\nYou can also manage this with submodules [2] or subtree-merge [3].\n\nI prefer submodules since it keeps the huge stuff (docs and bins) away\nfrom my source code and makes my source code repo much more responsive.\n\n[1] http://www.braintreepayments.com/devblog/our-git-workflow\n[2] http://progit.org/book/ch6-6.html\n[3] http://progit.org/book/ch6-7.html\n\nHTH,\nPhil\n"},{"id":"172164","messageId":"j0p7pc$q51$2@dough.gmane.org","threadId":"27932","inReplyTo":"4E302229.4030402@cisco.com","subject":"Re: Special branch for remote","fromName":"Paulo J. Matos","fromEmail":"paulo@matos-sorge.com","sentAt":"2011-07-27T14:36:28Z","receivedAt":"2011-07-27T14:36:28Z","isPatch":false,"sender":{"key":"paulo@matos-sorge.com","avatar":"https://gravatar.com/avatar/0877e386c336b900d05542bb71a10a85c15b96f5b13f28c334e492c0de9cd5bf?d=mp&s=160"},"body":"On 27/07/11 15:35, Phil Hord wrote:\n>\n> You can also manage this with submodules [2] or subtree-merge [3].\n>\n> I prefer submodules since it keeps the huge stuff (docs and bins) away\n> from my source code and makes my source code repo much more responsive.\n>\n\nThanks Phil, I will be looking at this solution then.\n\nCheers,\n-- \nPMatos\n"}]}