{"thread":{"id":"32120","subject":"use cases for git namespaces","startedAt":"2012-11-15T08:33:32Z","lastAt":"2012-11-15T12:39:03Z","messageCount":2,"participants":["Sitaram Chamarty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"203279","messageId":"CAMK1S_gczLajro0aZ5ftUmt_vhxA+yAr_5pCZknJ2bxhykYRXQ@mail.gmail.com","threadId":"32120","inReplyTo":null,"subject":"use cases for git namespaces","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2012-11-15T08:33:32Z","receivedAt":"2012-11-15T08:33:32Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"Hi,\n\nIt seems to me that whatever namespaces can do, can functionally be\ndone using just a subdirectory of branches.   The only real\ndifferences I can see are (a) a client sees less branch clutter, and\n(b) a fetch/clone pulls down less if the big stuff is in another\nnamespace.\n\nI would like to understand what other uses/reasons were thought of.\n\nI looked for discussion on the ml archives.  I found the patch series\nbut could not easily find much *discussion* of the feature and its\ndesign.  I found one post [1] that indicated that \"part of the\nrationale...\" (being what I described above), but I would like to\nunderstand the *rest* of the rationale.\n\nPointers to gmane are also fine, or brief descriptions of uses [being]\nmade of this.\n\n[1]: http://article.gmane.org/gmane.comp.version-control.git/175832/match=namespace\n\nThanks\n\n-- \nSitaram\n"},{"id":"203288","messageId":"CAMK1S_iWZyH5j7GdGj7Fuj=kn+zZ0wCZTSFXxjspGpcA+x-iSw@mail.gmail.com","threadId":"32120","inReplyTo":"CAMK1S_gczLajro0aZ5ftUmt_vhxA+yAr_5pCZknJ2bxhykYRXQ@mail.gmail.com","subject":"Re: use cases for git namespaces","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2012-11-15T12:39:03Z","receivedAt":"2012-11-15T12:39:03Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Thu, Nov 15, 2012 at 2:03 PM, Sitaram Chamarty <sitaramc@gmail.com> wrote:\n> Hi,\n>\n> It seems to me that whatever namespaces can do, can functionally be\n> done using just a subdirectory of branches.   The only real\n> differences I can see are (a) a client sees less branch clutter, and\n> (b) a fetch/clone pulls down less if the big stuff is in another\n> namespace.\n>\n> I would like to understand what other uses/reasons were thought of.\n\n(I should mention that I am asking from the client perspective.  I\nknow that on the server this has potential to save a lot of disk\nspace).\n\n> I looked for discussion on the ml archives.  I found the patch series\n> but could not easily find much *discussion* of the feature and its\n> design.  I found one post [1] that indicated that \"part of the\n> rationale...\" (being what I described above), but I would like to\n> understand the *rest* of the rationale.\n>\n> Pointers to gmane are also fine, or brief descriptions of uses [being]\n> made of this.\n>\n> [1]: http://article.gmane.org/gmane.comp.version-control.git/175832/match=namespace\n>\n> Thanks\n>\n> --\n> Sitaram\n\n\n\n-- \nSitaram\n"}]}