Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Mon, Oct 3, 2011 at 8:02 PM, Edward Ned Harvey <blu at nedharvey.com> wrote: > > From: discuss-bounces+blu=nedharvey.com at blu.org [mailto:discuss- > > bounces+blu=nedharvey.com at blu.org] On Behalf Of Jerry Feldman > > > > I currently have a bare git repository as well as a populated git > > repository. What I would like to do is to create a partial repository > > that contains a subset. > > In the main repo, I have a.c, b.c, c.c, d.c. e.c > > But I just want to create another repo containing only a.c, b.c and c.c > > for development purposes. > Jerry, It sound like you just want to make a branch, not a whole different repository. With a branch you can easily merge changes to b.c among the different branches, and you can easily switch branches to try out the code that doesn't have d.c > --------- > > Another solution is to split the master repo into the stuff that is > > under development, and the stuff that is unrelated from a project > > standpoint so it is probably better to create a second master bare repo, > > then remove the objects that do not apply to the project in one, and > > remove the project objects in the other. > Again it sounds like a branch strategy might help. git branch -a * master [1] kitchen_sink [2] [1] code that does stuff. The asterisk indicates it's the branch you're on in your working tree [2] master plus miscellaneous stuff that isn't actually part of the product/project
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |