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

shallow clones, was Re: What's cooking in git.git (topics)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 7, 2006, 14:59 UTC
Message-ID
<Pine.LNX.4.63.0612071557580.28348@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<87zma06ptm.fsf@wine.dyndns.org>
Hi,
On Thu, 7 Dec 2006, Alexandre Julliard wrote:
Show 17 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> >> * 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.
> 
> I'm not sure what reaction you expect, but this is something a lot of 
> our occasional Wine users are requesting. The Wine full history is 80Mb, 
> and that's a big download if you just want to try a quick patch. Now of 
> course you won't see these users around here hacking on shallow clone, 
> most likely they just went and downloaded Wine from the CVS mirror 
> instead. But it's a shame to have to maintain a CVS mirror just for that 
> purpose...

Sorry, I was just mumbling about the fact that I would _like_ to hear back about successes and failures. If there are problems I want to fix them.

So, do you actually know of people who _used_ (as opposed to "tested") shallow clones?

Ciao, Dscho

Previous: Alexandre JulliardNext: Alexandre Julliard
Message 6 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.