From: "Ефимов Василий" <real@ispras.ru>
To: git@vger.kernel.org
Subject: Bug: cherry-pick & submodule
Date: Fri, 10 Nov 2017 19:00:25 +0300 [thread overview]
Message-ID: <c48bf9f3-10b2-dfac-a207-74a57e66b848@ispras.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
I faced an unexpected behaviour during cherry-picking
a commit to a branch with a submodule.
Git graph:
A -- B [master]
\
`- C -- D [test]
Both branches have a file with name `a_file`.
It has been added by commit A.
Commits B and C add a folder with name `a_submodule` to the respective
branches.
Commit C does it regularly by adding a file with name `a_submodule/content`.
Commit B adds a submodule with name `a_submodule`.
Commit D only modifies `a_file`.
Note that `a_file` and `a_submodule` are not related.
[repo]
|- a_file
`- a_submodule
When I trying to cherry pick commit D on commit B, I got
a conflict with `a_submodule`. Changes of `a_file` are
successfully cherry-picked.
I expected, that there would be no conflicts.
A bash script reproducing the bug is attached.
Vasily.
[-- Attachment #2: bug.sh --]
[-- Type: application/x-shellscript, Size: 800 bytes --]
next reply other threads:[~2017-11-10 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 16:00 Ефимов Василий [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-10 16:41 Bug: cherry-pick & submodule Ефимов Василий
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=c48bf9f3-10b2-dfac-a207-74a57e66b848@ispras.ru \
--to=real@ispras.ru \
--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).