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

Re: Tracking a repository for content instead of history

From
APAndy Parkins <andyparkins@gmail.com>
Date
Dec 12, 2006, 15:38 UTC
Message-ID
<200612121538.41197.andyparkins@gmail.com>
In-Reply-To
<Pine.LNX.4.63.0612121527070.2807@wbgn013.biozentrum.uni-wuerzburg.de>
On Tuesday 2006 December 12 14:28, Johannes Schindelin wrote:
> You are not by any chance talking about the --remote option to
> git-archive?
I wasn't; but that's certainly a helpful switch.  It's certainly a huge help.
> If you want to reduce the number of objects to be downloaded, by telling
> the other side what you have, you literally end up with something like
> shallow clone: the other side _has_ to support it.

I suppose so; but I was thinking more an automated way of getting the data that is supplied for the kernel anyway. So:

base-v1.0.0.tar.gz patch-v1.0.1.gz patch-v1.0.2.gz etc

Each patch is obviously smaller than "base". Git could easily make the patches, and each of those patches could be fed by hand into a repository with git-apply. It doesn't seem like something that would require support on the other side, because it isn't so much a shallow clone (which /would/ preserve history, making it available if wanted); it is pulling just, say, tagged commits out of an existing repository.

Given a list of tags it is almost:

git-archive <get me base> ssh remote git-diff v1.0.0..v1.0.1 | git-apply; git commit ssh remote git-diff v1.0.1..v1.0.2 | git-apply; git commit

If that makes sense? Obviously though it would be possible to use git rather than ssh to do this.

However... please don't waste any more time thinking about this; it's not a problem I have that needs a solution - it was more a "because I'm curious" sort of question.

Andy
-- 
Dr Andy Parkins, M Eng (hons), MIEE
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 5 of 10 in “Tracking a repository for content instead of history”
  1. Andy ParkinsDec 12, 2006
  2. Jakub NarebskiDec 12, 2006
  3. Andy ParkinsDec 12, 2006
  4. Johannes SchindelinDec 12, 2006
  5. Andy ParkinsDec 12, 2006
  6. Johannes SchindelinDec 12, 2006
  7. Johannes SchindelinDec 12, 2006
  8. Nguyen Thai Ngoc DuyDec 12, 2006
  9. Nguyen Thai Ngoc DuyDec 12, 2006
  10. Johannes SchindelinDec 12, 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.