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

Re: Tracking a repository for content instead of history

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Dec 12, 2006, 21:48 UTC
Message-ID
<fcaeb9bf0612121348q35549a4cof0adb85e0391b92c@mail.gmail.com>
In-Reply-To
<fcaeb9bf0612121346s3c82bcdbh522c17f4ae9f279b@mail.gmail.com>
On 12/13/06, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
Show 6 quoted lines
> Hm.. I'm no git:// expert. But is it possible doing as follow?
> 1. git-archive <base>
> 2. reconstruct commit, blobs and trees from the archive
> 3. tell git server that you have one commit, you need another commit
> (maybe heads only, i'm not sure here)
> 4. get the pack from git server, create new commit and a diff
Ok. Stupid idea. The pack may base on objects that I don't have.
Previous: Nguyen Thai Ngoc DuyNext: Johannes Schindelin
Message 9 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.