{"thread":{"id":"14935","subject":"clone branching?","startedAt":"2008-08-11T18:24:23Z","lastAt":"2008-08-12T07:34:35Z","messageCount":4,"participants":["Trans","Miklos Vajna","Karl Hasselström"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"86800","messageId":"4b6f054f0808111124g58309f64v496ceb250a068985@mail.gmail.com","threadId":"14935","inReplyTo":null,"subject":"clone branching?","fromName":"Trans","fromEmail":"transfire@gmail.com","sentAt":"2008-08-11T18:24:23Z","receivedAt":"2008-08-11T18:24:23Z","isPatch":false,"sender":{"key":"transfire@gmail.com","avatar":"https://gravatar.com/avatar/f98ccb7e9a9a79b343086463300c72cc330cf53bc5731867b662874c9fe1ccca?d=mp&s=160"},"body":"Hi,\n\nI'm new to this list and evaluating whether to use Git. On the whole I\nreally like Git, however, I'm not sure l like the way it handles\nbranching.\n\nCan Git be effectively used if clone is used for branching, rather\nthen using the internal branch naming?\n\nThanks,\nT.\n"},{"id":"86814","messageId":"20080811191727.GS18960@genesis.frugalware.org","threadId":"14935","inReplyTo":"4b6f054f0808111124g58309f64v496ceb250a068985@mail.gmail.com","subject":"Re: clone branching?","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2008-08-11T19:17:27Z","receivedAt":"2008-08-11T19:17:27Z","isPatch":false,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Mon, Aug 11, 2008 at 02:24:23PM -0400, Trans <transfire@gmail.com> wrote:\n> Can Git be effectively used if clone is used for branching, rather\n> then using the internal branch naming?\n\nSee git clone -l.\n\nYou can also use git clone -s (but it may be dangerous, more info in the\nmanpage) and git-new-workdir (but that's only in contrib, you may have\nissues with it).\n"},{"id":"86824","messageId":"20080811203917.GA20662@diana.vm.bytemark.co.uk","threadId":"14935","inReplyTo":"4b6f054f0808111124g58309f64v496ceb250a068985@mail.gmail.com","subject":"Re: clone branching?","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2008-08-11T20:39:17Z","receivedAt":"2008-08-11T20:39:17Z","isPatch":false,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"On 2008-08-11 14:24:23 -0400, Trans wrote:\n\n> I'm new to this list and evaluating whether to use Git. On the whole\n> I really like Git, however, I'm not sure l like the way it handles\n> branching.\n>\n> Can Git be effectively used if clone is used for branching, rather\n> then using the internal branch naming?\n\nYes, definitely.\n\ngit supports multiple branches per repository/working copy, but\ndoesn't force you to have more than one. And it's very easy to pull\nchanges from one repo to another.\n\n-- \nKarl Hasselström, kha@treskal.com\n      www.treskal.com/kalle\n"},{"id":"86907","messageId":"20080812073435.GA30811@diana.vm.bytemark.co.uk","threadId":"14935","inReplyTo":"4b6f054f0808111324x5a7c44afj6f93bc1e36fc481a@mail.gmail.com","subject":"Re: clone branching?","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2008-08-12T07:34:35Z","receivedAt":"2008-08-12T07:34:35Z","isPatch":false,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"On 2008-08-11 16:24:57 -0400, Trans wrote:\n\n> On Mon, Aug 11, 2008 at 4:39 PM, Karl Hasselström <kha@treskal.com>\n> wrote:\n>\n> > git supports multiple branches per repository/working copy, but\n> > doesn't force you to have more than one. And it's very easy to\n> > pull changes from one repo to another.\n>\n> In retrospect, It's more the tags I need rather then branches, but\n> just the same... So if I have a repository like:\n>\n>   myapp/\n>     1.0.0/\n>     1.0.1/\n>     1.1.0/\n>     current/\n>\n> This would be okay? No other \"giter\" is going to look at this and\n> think \"what the hell?\"\n\nThat would be OK. But \"myapp\" wouldn't be a repository -- it'd be a\ndirectory that contains four repositories. Each of those repositories\nwould have a specific branch checked out, but they'd probably all\ncontain the full set of tags and branches.\n\n> Hmm... actually I don't see how this can work. If .get is under\n> current/ than no one will be able to see the tags on my shared repo,\n> but if it is under myapp/ then I'd be branching and tagging my tags\n> --that's doesn't make any sense. I'm confused.\n\nAll your repositories have a .git directory. That's what makes them\ngit reppositories.\n\nI think what you need to do to get un-confused is to learn about how\ngit stores history. Specifically, that\n\n  1. the history consists of a DAG of commits, and\n\n  2. that branches and tags are just named pointers to commits.\n\nhttp://eagain.net/articles/git-for-computer-scientists/ is a short and\nsweet introduction.\n\n-- \nKarl Hasselström, kha@treskal.com\n      www.treskal.com/kalle\n"}]}