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, 07:16 UTC
Message-ID
<cdea6cd10907170016u11af7230hbbee92682604530f@mail.gmail.com>
In-Reply-To
<32541b130907161527l1955bf06pf54b5099a5988c65@mail.gmail.com>
On Fri, Jul 17, 2009 at 2:27 AM, Avery Pennarun<apenwarr> wrote:
Show 5 quoted lines
>> The only thing that links git-subtree with git-rebase is the fact, that
>> git-subtree "knows" the target commit for rebases dealing with subtrees.
> rebase doesn't
> have any parameters called a "target."  What does git-subtree know
> that you don't know?

By "rebase target" I mean the mutual relation of git-rebase <newbase> and <upstream> paramaters that define where will be the rebased commits. git-subtree can infer that NewProj contains library up to test-split and that OldProj contains library upto test-split-old. The concept of the whole git-subtee workflow is still blurry to me though, so I will report when I gather more usage statistics.

> I don't really understand what you're asking for here.

At most I need generic ability to shift merged and rebased repository's or ref's "left" (selecting some directory or file) and "right" (prepending some directory to all paths) before actual operation(s). I.e. the antonym of 'split' but without 'add' committree-joining semantics. This can be implemented with some chaining/plumbing presets.

-- Sincerly yours, Andrey.

Previous: Avery PennarunNext: Avery Pennarun
Message 11 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.