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

Re: What's cooking in git.git (topics)

From
APAndy Parkins <andyparkins@gmail.com>
Date
Dec 7, 2006, 17:49 UTC
Message-ID
<200612071749.17849.andyparkins@gmail.com>
In-Reply-To
<Pine.LNX.4.63.0612070035570.28348@wbgn013.biozentrum.uni-wuerzburg.de>
On Wednesday 2006, December 06 23:42, Johannes Schindelin wrote:
Show 7 quoted lines
> > * js/shallow (Fri Nov 24 16:00:13 2006 +0100)
> >
> >  Probably with a better documentation of its limitations and caveats,
> >  this should be mergeable to 'master'.
>
> The more I see the missing reaction, the less sure I am this is a sensible
> thing to do.

Don't be too downhearted. I am certainly looking forward to using shallow clones; but by their very nature they are going to be used on big established projects (otherwise why would one need a shallow clone?), so until those projects upgrade their servers the news will be quiet

Also; it's probably going to be casual developers that find shallow clones useful, as the main developers will clone the whole repository. This might also mean that they aren't going to be around on the git mailing list.

I certainly wouldn't say that the shallow clone work is not being appreciated. It's just being appreciated quietly.

Andy
-- 
Dr Andrew Parkins, M Eng (Hons), AMIEE
Previous: Aneesh Kumar K.V
Message 9 of 9 in “What's cooking in git.git (topics)”
  1. Junio C HamanoDec 6, 2006
  2. Jakub NarebskiDec 6, 2006
  3. Junio C HamanoDec 6, 2006
  4. Johannes SchindelinDec 6, 2006
  5. Alexandre JulliardDec 7, 2006
  6. shallow clones, was Re: What's cooking in git.git (topics)Johannes Schindelin, Dec 7, 2006
  7. Alexandre JulliardDec 7, 2006
  8. Aneesh Kumar K.VDec 8, 2006
  9. Andy ParkinsDec 7, 2006

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.