From: Jason Karns <jason.karns@gmail.com>
To: git@vger.kernel.org
Subject: Confusion regarding subtree-push docs
Date: Sun, 22 Mar 2020 13:57:28 -0400 [thread overview]
Message-ID: <29B972A3-277C-413F-A387-056AD80C169F@gmail.com> (raw)
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
reply other threads:[~2020-03-22 17:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29B972A3-277C-413F-A387-056AD80C169F@gmail.com \
--to=jason.karns@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).