-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
local_working_copy: when all sides of a conflict are executable, mate… #3580
local_working_copy: when all sides of a conflict are executable, mate… #3580
Conversation
The new test fails before the fix and passes after it. This repro script can also be used to verify: #!/usr/bin/env bash
mkdir repro_permfail
cd repro_permfail/
jj git init
cat <<EOF > script.sh
#!/usr/bin/bash
echo "No conflict here."
EOF
chmod 755 script.sh
jj desc -m "script import"
jj new -m "set up for conflict"
jj branch create setup-conflict
cat <<EOF >> script.sh
echo "Half a conflict."
EOF
jj new -r @- -m "create a conflict"
cat <<EOF >> script.sh
echo "The other half."
EOF
jj rebase -d setup-conflict |
9d5d743
to
00b1912
Compare
Thanks for the reviews. I've addressed the feedback, and added a second commit which fixes some clippy warnings which were output only on windows - turns out that the |
Thanks. I suppose we could also run clippy on windows. Not sure it's worth the resource cost given how infrequently it's going to find anything. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
…rialise the conflicted file as executable Fixes jj-vcs#3579 and adds a testcase for an executable conflict treevalue.
00b1912
to
8739434
Compare
local_working_copy: when all sides of a conflict are executable, materialise the conflicted file as executable
Fixes #3579 and adds a testcase for an executable conflict treevalue.