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

Re: [PATCH/RFC 1/2] Add 'git subtree' command for tracking history of subtrees separately.

From
ASAndrey Smirnov <allter@gmail.com>
Date
Jul 17, 2009, 17:46 UTC
Message-ID
<cdea6cd10907171046u257fa8ebjee445a90de0a282c@mail.gmail.com>
In-Reply-To
<32541b130907170847g67c89d54ke9426ed8da26a9aa@mail.gmail.com>
On Fri, Jul 17, 2009 at 7:47 PM, Avery Pennarun<apenwarr@gmail.com> wrote:
> The problem is that test-split and test-split-old are completely
> unrelated trees that have similar-looking files but no common
> ancestry.

I understand this but if two projects share the same commit history for their subdir-lib both test-split and test-split-old will have same root.

> git-rebase tries to be cleverer, and starts comparing patches and file
> similarities so it can graft one tree onto another,

That is too clear for me and since I try to avoid committing 'reversion commits' it works for my workflow. I don't want to track library as separate ref (at least now).

Anyway thank you for great extension - will now try using it on a regular basis - there're another project that is more suitable to track libraries as you suggest.

-- Sincerly yours, Andrey.

Previous: Avery Pennarun
Message 13 of 13 in “Add 'git subtree' command for tracking history of subtrees separately.”
  1. 1/2 Add 'git subtree' command for tracking history of subtrees separately.Avery Pennarun, Apr 26, 2009
  2. 2/2 Automated test script for 'git subtree'.Avery Pennarun, Apr 26, 2009
  3. Avery PennarunApr 30, 2009
  4. Ping YinApr 30, 2009
  5. Finn Arne GangstadApr 30, 2009
  6. Avery PennarunApr 30, 2009
  7. Andrey SmirnovJul 16, 2009
  8. Avery PennarunJul 16, 2009
  9. Andrey SmirnovJul 16, 2009
  10. Avery PennarunJul 16, 2009
  11. Andrey SmirnovJul 17, 2009
  12. Avery PennarunJul 17, 2009
  13. Andrey SmirnovJul 17, 2009

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.