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

git filter-branch and superproject

From
Sergio Callegari <sergio.callegari@gmail.com>
Date
Dec 16, 2008, 11:56 UTC
Message-ID
<loom.20081216T114923-354@post.gmane.org>
Hi,

once a sub-project has been rewritten by filter branch, there is a problem with references in superproject.

This is obviously a case where something "has been published" so filter-branch is not a good idea. However, super-projects are a very special case of publication since they might be "in full control" of whom did the rewriting of their submodules.

Is there a way to filter branch the superproject so that whatever commit is referenced that is in refs/original/something in the subproject gets updated to the corresponding rewritten commit (or an error is given if such a correspondance does not exist)?

Namely, can filter-branch on the subproject deliver a "commit conversion table" that can then be fed to a filter-branch in a superproject?

Next: Boaz Harrosh
Message 1 of 2 in “git filter-branch and superproject”
  1. Sergio CallegariDec 16, 2008
  2. Boaz HarroshDec 16, 2008

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.