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

Confusion regarding subtree-push docs

From
Jason Karns <jason.karns@gmail.com>
Date
Mar 22, 2020, 17:57 UTC
Message-ID
<29B972A3-277C-413F-A387-056AD80C169F@gmail.com>
I found some of git-subtree-push’s behavior confusing as it pertains to the docs. (Using git version 2.25.1)
The docs for subtree-push state: (https://github.com/git/git/blob/master/contrib/subtree/git-subtree.txt)
>  Does a 'split' (see below) using the <prefix> supplied and then does a 'git push' to push the result to the repository and ref.
As I understood this, I expected push to do a split “under the covers”. As such, I expected the relevant `split` options to be respected by push as well. In particular, I expected —annotate to modify the split+push commits with the corresponding prefix. Additionally, I expected subtree-push to also respect —rejoin and merge back into HEAD.
I think the docs as they are written are a bit misleading; or perhaps the docs are accurate and this is a bug with subtree-push? The former is more likely, so I assume the docs should be rephrased to make this clear. (Unless the docs are accurate and this is a bug with subtree-push.)

Regards, Jason

Message 1 of 1 in “Confusion regarding subtree-push docs”
  1. Jason KarnsMar 22, 2020

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.