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

Re: What's in git.git

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 2, 2006, 10:02 UTC
Message-ID
<Pine.LNX.4.63.0611021055550.1670@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<7vk62ewtxd.fsf@assigned-by-dhcp.cox.net>
Hi,
On Wed, 1 Nov 2006, Junio C Hamano wrote:
Show 7 quoted lines
> * The 'pu' branch, in addition, has these.
> 
>   Johannes's "shallow" was marked as "pu" material so I've based
>   the series on the tip of "next" (which means we cannot
>   directly merge that into "next" or "master" without rebasing
>   it to "master" first) and parked it in "pu".  I have given
>   only a cursory look to it but it looks promising.

Note that I have no use for shallow clones myself, since I really like to have the complete history around. It also makes for a nice distributed backup solution.

The reasons I did it:
- 'cause I could
- I think it is important for other people (this means you, Jon)
- I suggested lazy clones as an easy way out, but I am now convinced that 
they introduce more problems than they solve. Therefore I wanted to make 
good for the confusion I helped develop.

Since I do not have any use for shallow clones myself, I am waiting for people to jump on it, test it, and shout "Hooray" or "Nacknacknack".

Ciao, Dscho

Previous: Junio C HamanoNext: Rene Scharfe
Message 2 of 4 in “What's in git.git”
  1. Junio C HamanoNov 2, 2006
  2. Johannes SchindelinNov 2, 2006
  3. Rene ScharfeNov 5, 2006
  4. Junio C HamanoNov 5, 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.