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

Re: Features from GitSurvey 2010

From
GBGeert Bosch <bosch@adacore.com>
Date
Feb 3, 2011, 14:38 UTC
Message-ID
<FE2BDD68-9CFA-4CBB-9F66-32BE6CF3E174@adacore.com>
In-Reply-To
<alpine.LFD.2.00.1102011647000.8580@xanadu.home>
On Feb 1, 2011, at 16:51, Nicolas Pitre wrote:
> Also... people interested in Narrow clones are likely to be shallow 
> clone users too, right?

Not necessarily. Many corporate repositories are huge (caused by the concept of 1 central repository with everything in it) and have tons of crud (like marketing materials, media-heavy powerpoint presentations). Here you really want a narrow clone (such as the sources of the project you're working on), but don't mind having the whole history.

Looking at it from another angle: typically the whole history of a project is not much bigger than a check out, so it is fine to have a deep history. On the other hand, for these monster repositories one would typically do a narrow clone of only a single subdirectory that may be more than an order of magnitude smaller.

These narrow clones are especially important for imports of unwieldy svn repositories where there is a large amount of unstructured branching.

Regards,
   -Geert
Previous: david@lang.hmNext: Jonathan Nieder
Message 16 of 36 in “Features from GitSurvey 2010”
  1. Dmitry S. KravtsovJan 29, 2011
  2. Jonathan NiederJan 29, 2011
  3. Jakub NarebskiFeb 1, 2011
  4. Nguyen Thai Ngoc DuyFeb 1, 2011
  5. Shawn PearceFeb 1, 2011
  6. Shawn PearceFeb 1, 2011
  7. Nguyen Thai Ngoc DuyFeb 1, 2011
  8. Junio C HamanoFeb 1, 2011
  9. Nicolas PitreFeb 1, 2011
  10. Nguyen Thai Ngoc DuyFeb 1, 2011
  11. Shawn PearceFeb 1, 2011
  12. Nicolas PitreFeb 1, 2011
  13. Shawn PearceFeb 2, 2011
  14. Nicolas PitreFeb 2, 2011
  15. david@lang.hmFeb 2, 2011
  16. Geert BoschFeb 3, 2011
  17. Narrow clone (Re: features from GitSurvey 2010)Jonathan Nieder, Feb 3, 2011
  18. Geert BoschFeb 3, 2011
  19. Jonathan NiederFeb 3, 2011
  20. Jonathan NiederFeb 3, 2011
  21. Nicolas PitreFeb 3, 2011
  22. Tracking empty directoriesJonathan Nieder, Feb 1, 2011
  23. Nguyen Thai Ngoc DuyFeb 1, 2011
  24. Ilari LiusvaaraFeb 1, 2011
  25. Jakub NarebskiFeb 1, 2011
  26. Ilari LiusvaaraFeb 1, 2011
  27. Jonathan NiederFeb 1, 2011
  28. Jakub NarebskiFeb 1, 2011
  29. Nguyen Thai Ngoc DuyFeb 2, 2011
  30. Kevin P. FlemingFeb 2, 2011
  31. Nicolas PitreFeb 1, 2011
  32. big files in git was: Re: Features from GitSurvey 2010david@lang.hm, Feb 1, 2011
  33. Nicolas PitreFeb 3, 2011
  34. Matthieu MoyFeb 1, 2011
  35. Jonathan NiederFeb 1, 2011
  36. Matthieu MoyFeb 1, 2011

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.