git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: use cases for git namespaces

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Nov 15, 2012, 12:39 UTC
Message-ID
<CAMK1S_iWZyH5j7GdGj7Fuj=kn+zZ0wCZTSFXxjspGpcA+x-iSw@mail.gmail.com>
In-Reply-To
<CAMK1S_gczLajro0aZ5ftUmt_vhxA+yAr_5pCZknJ2bxhykYRXQ@mail.gmail.com>
On Thu, Nov 15, 2012 at 2:03 PM, Sitaram Chamarty <sitaramc@gmail.com> wrote:
Show 9 quoted lines
> Hi,
>
> It seems to me that whatever namespaces can do, can functionally be
> done using just a subdirectory of branches.   The only real
> differences I can see are (a) a client sees less branch clutter, and
> (b) a fetch/clone pulls down less if the big stuff is in another
> namespace.
>
> I would like to understand what other uses/reasons were thought of.

(I should mention that I am asking from the client perspective. I know that on the server this has potential to save a lot of disk space).

Show 15 quoted lines
> I looked for discussion on the ml archives.  I found the patch series
> but could not easily find much *discussion* of the feature and its
> design.  I found one post [1] that indicated that "part of the
> rationale..." (being what I described above), but I would like to
> understand the *rest* of the rationale.
>
> Pointers to gmane are also fine, or brief descriptions of uses [being]
> made of this.
>
> [1]: http://article.gmane.org/gmane.comp.version-control.git/175832/match=namespace
>
> Thanks
>
> --
> Sitaram
-- 
Sitaram
Previous: Sitaram Chamarty
Message 2 of 2 in “use cases for git namespaces”
  1. Sitaram ChamartyNov 15, 2012
  2. Sitaram ChamartyNov 15, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.