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

Re: Git User's Survey 2008 partial summary, part 5 - other SCM

From
Jakub Narebski <jnareb@gmail.com>
Date
Sep 16, 2008, 17:12 UTC
Message-ID
<200809161912.06571.jnareb@gmail.com>
In-Reply-To
<alpine.DEB.1.10.0809142038190.19489@asgard.lang.hm>
On Mon, 15 Sep 2008, David Lang <david@lang.hm> napisał:
Show 26 quoted lines
> On Sun, 14 Sep 2008, Nguyen Thai Ngoc Duy wrote:
>> On 9/12/08, Jakub Narebski <jnareb@gmail.com> wrote:
>>>  15) Do you miss features in git that you know from other SCMs?
>>>     If yes, what features are these (and from which SCM)?
>>>     (Open ended text - Essay)
>>>
>>>  Total respondents       1046 (some/many of them wrote 'no')
>>>  skipped this question   1249
>>>
>>>  This is just a very quick summary, based on a first few pages of
>>>  responses, Full analysis is I think best left for after closing the
>>>  survey, because I think this would be a lot of work...
>>>
>>>  So here is preliminary list, or rather beginning of one:
>>>   * sparse/partial checkout and clone (e.g. Perforce)
>>
>> Have not read the survey result, but do you recall what is the most
>> used term for sparse/partial checkout? What SCMs do sparse/partial
>> checkout? I think it could be usable as it is now in my
>> will-be-sent-again series, but I don't really know how people want it
>> to from that.
> 
> the most common use-case is people who want to follow a project but
> (at least think that they) don't need the history. so they want to
> save time/bandwideth/disk space by not downloading things they don't
> need. 

Errr... the idea is to implement partial (sparse, narrow) _checkout_, which is doable, not partial/lazy _clone_, which is very, very difficult.

Partial checkout *might* help reduce disk space because usually repository database (which is compressed and deltaified) is smaller than checkout; and if it isn't you can always use _shallow_ clone (only part of history) and/or remote alternates (with reference repository not on your quota, or on different filesystem). And it might help checkout/commit/diff/status times (performance) on slow filesystems, with extremely large number of files in full checkout. But contrary to centralized SCM, where server is usually net away from working area, partial checkout doesn't affect network usage _at all_.

-- 
Jakub Narebski
Poland
Previous: Andreas EricssonNext: Jakub Narebski
Message 32 of 33 in “Git User's Survey 2008 partial summary”
  1. Jakub NarebskiSep 3, 2008
  2. Shawn O. PearceSep 3, 2008
  3. H.Merijn BrandSep 3, 2008
  4. Felipe ContrerasSep 3, 2008
  5. David AguilarSep 4, 2008
  6. Jan HudecSep 5, 2008
  7. David AguilarSep 6, 2008
  8. David BrownSep 3, 2008
  9. Scott ChaconSep 3, 2008
  10. Jakub NarebskiSep 3, 2008
  11. Jakub NarebskiSep 4, 2008
  12. Git User's Survey 2008 partial summary, part 3Jakub Narebski, Sep 6, 2008
  13. Shawn O. PearceSep 6, 2008
  14. Andreas EricssonSep 6, 2008
  15. Jonas FonsecaSep 7, 2008
  16. Shawn O. PearceSep 7, 2008
  17. Git User's Survey 2008 partial summary, part 4 - how do we use GitJakub Narebski, Sep 6, 2008
  18. Andreas EricssonSep 7, 2008
  19. Jakub NarebskiSep 7, 2008
  20. Git User's Survey 2008 partial summary, part 5 - other SCMJakub Narebski, Sep 11, 2008
  21. Anatol PomozovSep 11, 2008
  22. Jeff KingSep 11, 2008
  23. david@lang.hmSep 11, 2008
  24. Jakub NarebskiSep 12, 2008
  25. david@lang.hmSep 13, 2008
  26. Jakub NarebskiSep 13, 2008
  27. Mark BrownSep 15, 2008
  28. Nguyen Thai Ngoc DuySep 14, 2008
  29. Jakub NarebskiSep 14, 2008
  30. david@lang.hmSep 15, 2008
  31. Andreas EricssonSep 15, 2008
  32. Jakub NarebskiSep 16, 2008
  33. Jakub NarebskiSep 11, 2008

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.