{"thread":{"id":"53060","subject":"Confusion regarding subtree-push docs","startedAt":"2020-03-22T17:57:34Z","lastAt":"2020-03-22T17:57:34Z","messageCount":1,"participants":["Jason Karns"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"393729","messageId":"29B972A3-277C-413F-A387-056AD80C169F@gmail.com","threadId":"53060","inReplyTo":null,"subject":"Confusion regarding subtree-push docs","fromName":"Jason Karns","fromEmail":"jason.karns@gmail.com","sentAt":"2020-03-22T17:57:28Z","receivedAt":"2020-03-22T17:57:34Z","isPatch":false,"sender":{"key":"jason.karns@gmail.com","avatar":"https://gravatar.com/avatar/c86e80bb1929ad0ea739f79f04d349adfa550d010fde1bd1ea413b6c277e850f?d=mp&s=160"},"body":"I found some of git-subtree-push’s behavior confusing as it pertains to the docs. (Using git version 2.25.1)\n\nThe docs for subtree-push state: (https://github.com/git/git/blob/master/contrib/subtree/git-subtree.txt)\n\n>  Does a 'split' (see below) using the <prefix> supplied and then does a 'git push' to push the result to the repository and ref.\n\nAs 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.\n\nI 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.)\n\nRegards,\nJason"}]}